Date: Thu, 6 Jul 2006 20:05:12 +0000 (+0000) Subject: fixup properties X-Git-Tag: 2.3.0~2288 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=459217fff2713575d069623c783db1790f4f6e5e;p=thirdparty%2Fapache%2Fhttpd.git fixup properties git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@419688 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_aspdotnet.xml b/docs/manual/mod/mod_aspdotnet.xml index 001e9ddf362..99c770cfea1 100644 --- a/docs/manual/mod/mod_aspdotnet.xml +++ b/docs/manual/mod/mod_aspdotnet.xml @@ -1,7 +1,7 @@ - + -Apache mod_rewrite Flags - Apache HTTP Server - - - - - -

-Apache > HTTP Server > Documentation > Version 2.3

Apache mod_rewrite Flags

Available Languages: en

- -

This document discusses the flags which are available to the -RewriteRule directive, -providing more detailed explanations and examples of each.

Introduction
The flags

Introduction

RewriteRules can have -their behavior modified by one or more flags. Flags are included in -square brackets at the end of the rule, and multiple flags are separated -by commas.

-RewriteRule pattern target [Flag1,Flag2,Flag3] -

- -

The flags all have a short form, such as CO, as well as -a longer form, such as cookie. Some flags take one or more -arguments. Flags are not case sensitive.

- -

The flags

- -

Each flag has a long and short form. While it is most common to use -the short form, it is recommended that you familiarize yourself with the -long form, so that you remember what each flag is supposed to do.

- -

Presented here are each of the available flags, along with an example -of how you might use them.

- -

C|chain

The [C] or [chain] flag indicates that the RewriteRule is chained to the next -rule. That is, if the rule matches, then it is processed as usual and -control moves on to the next rule. However, if it does not match, then -the next rule, and any other rules that are chained together, will be -skipped.

- - - -

CO|cookie

The [CO], or [cookie] flag, allows you to set a cookie when a -particular RewriteRule -matches. The argument consists of three required fields and two optional -fields.

You must declare a name and value for the cookie to be set, and the -domain for which you wish the cookie to be valid. You may optionally set -the lifetime of the cookie, and the path for which it should be -returned.

By default, the lifetime of the cookie is the current browser -session.

By default, the path for which the cookie will be valid is "/" - that -is, the entire website.

Several examples are offered here:

- -

-RewriteEngine On -RewriteRule ^/index.html - [CO=frontdoor=yes:.apache.org:1440:/] -

- -

This rule doesn't rewrite the request (the "-" rewrite target tells -mod_rewrite to pass the request through unchanged) but sets a cookie -called 'frontdoor' to a value of 'yes'. The cookie is valid for any host -in the .apache.org domain. It will be set to expire in 1440 -minutes (24 hours) and will be returned for all URIs.

- - - -

E|env

With the [E], or [env] flag, you can set the value of an environment -variable. Note that some environment variables may be set after the rule -is run, thus unsetting what you have set. See the -Environment Variables document for more details on how Environment -variables work.

- -

The following example sets an evironment variable called 'image' to a -value of '1' if the requested URI is an image file. Then, that -environment variable is used to exclude those requests from the access -log.

- -

-RewriteRule %{REQUEST_URI} \.(png|gif|jpg) - [E=image:1] -CustomLog logs/access_log combined env=!image -

- -

Note that this same effect can be obtained using SetEnvIf. This technique is offered as -an example, not as a recommendation.

- - -

F|forbidden

Forbidden flag

- - -

G|gone

Gone flag

- - -

H|handler

Handler flag

- - -

L|last

Last flag

- - -

N|next

Next round flag

- - -

NC|nocase

No case flag

- - -

NE|noescape

No escape flag

- - -

NS|nosubreq

No internal subrequest flag

- - -

P|proxy

Proxy flag

- - -

PT|passthrough

Passthrough flag

- - -

PT|passthrough

Passthrough flag

- - -

QSA|qsappend

Query String Append flag

- - -

R|redirect

Redirect flag

- - -

S|skip

Skip flag

- - -

T|type

Type flag

- - -

Available Languages: en

+ + + +Apache mod_rewrite Flags - Apache HTTP Server + + + + + +

+Apache > HTTP Server > Documentation > Version 2.3

Apache mod_rewrite Flags

Available Languages: en

+ +

This document discusses the flags which are available to the +RewriteRule directive, +providing more detailed explanations and examples of each.

Introduction
The flags

Introduction

RewriteRules can have +their behavior modified by one or more flags. Flags are included in +square brackets at the end of the rule, and multiple flags are separated +by commas.

+RewriteRule pattern target [Flag1,Flag2,Flag3] +

+ +

The flags all have a short form, such as CO, as well as +a longer form, such as cookie. Some flags take one or more +arguments. Flags are not case sensitive.

+ +

The flags

+ +

Each flag has a long and short form. While it is most common to use +the short form, it is recommended that you familiarize yourself with the +long form, so that you remember what each flag is supposed to do.

+ +

Presented here are each of the available flags, along with an example +of how you might use them.

+ +

C|chain

The [C] or [chain] flag indicates that the RewriteRule is chained to the next +rule. That is, if the rule matches, then it is processed as usual and +control moves on to the next rule. However, if it does not match, then +the next rule, and any other rules that are chained together, will be +skipped.

+ + + +

CO|cookie

The [CO], or [cookie] flag, allows you to set a cookie when a +particular RewriteRule +matches. The argument consists of three required fields and two optional +fields.

You must declare a name and value for the cookie to be set, and the +domain for which you wish the cookie to be valid. You may optionally set +the lifetime of the cookie, and the path for which it should be +returned.

By default, the lifetime of the cookie is the current browser +session.

By default, the path for which the cookie will be valid is "/" - that +is, the entire website.

Several examples are offered here:

+ +

+RewriteEngine On +RewriteRule ^/index.html - [CO=frontdoor=yes:.apache.org:1440:/] +

+ +

This rule doesn't rewrite the request (the "-" rewrite target tells +mod_rewrite to pass the request through unchanged) but sets a cookie +called 'frontdoor' to a value of 'yes'. The cookie is valid for any host +in the .apache.org domain. It will be set to expire in 1440 +minutes (24 hours) and will be returned for all URIs.

+ + + +

E|env

With the [E], or [env] flag, you can set the value of an environment +variable. Note that some environment variables may be set after the rule +is run, thus unsetting what you have set. See the +Environment Variables document for more details on how Environment +variables work.

+ +

The following example sets an evironment variable called 'image' to a +value of '1' if the requested URI is an image file. Then, that +environment variable is used to exclude those requests from the access +log.

+ +

+RewriteRule %{REQUEST_URI} \.(png|gif|jpg) - [E=image:1] +CustomLog logs/access_log combined env=!image +

+ +

Note that this same effect can be obtained using SetEnvIf. This technique is offered as +an example, not as a recommendation.

+ + +

F|forbidden

Forbidden flag

+ + +

G|gone

Gone flag

+ + +

H|handler

Handler flag

+ + +

L|last

Last flag

+ + +

N|next

Next round flag

+ + +

NC|nocase

No case flag

+ + +

NE|noescape

No escape flag

+ + +

NS|nosubreq

No internal subrequest flag

+ + +

P|proxy

Proxy flag

+ + +

PT|passthrough

Passthrough flag

+ + +

PT|passthrough

Passthrough flag

+ + +

QSA|qsappend

Query String Append flag

+ + +

R|redirect

Redirect flag

+ + +

S|skip

Skip flag

+ + +

T|type

Type flag

+ + +

Available Languages: en

\ No newline at end of file diff --git a/docs/manual/rewrite/flags.xml b/docs/manual/rewrite/flags.xml index 3b11fda013f..cc5012f9f5d 100644 --- a/docs/manual/rewrite/flags.xml +++ b/docs/manual/rewrite/flags.xml @@ -1,7 +1,7 @@ - +

Apache mod_rewrite Flags

See also

Apache mod_rewrite Flags

See also