Return-Path: Delivered-To: apmail-httpd-cvs-archive@www.apache.org Received: (qmail 27700 invoked from network); 6 Jul 2006 20:05:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jul 2006 20:05:36 -0000 Received: (qmail 91579 invoked by uid 500); 6 Jul 2006 20:05:36 -0000 Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org Received: (qmail 91379 invoked by uid 500); 6 Jul 2006 20:05:35 -0000 Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list cvs@httpd.apache.org Received: (qmail 91368 invoked by uid 99); 6 Jul 2006 20:05:35 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jul 2006 13:05:35 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jul 2006 13:05:34 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id 3BD591A981A; Thu, 6 Jul 2006 13:05:14 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r419688 - in /httpd/httpd/trunk/docs/manual: mod/mod_aspdotnet.xml rewrite/flags.html rewrite/flags.html.en rewrite/flags.xml rewrite/flags.xml.meta Date: Thu, 06 Jul 2006 20:05:13 -0000 To: cvs@httpd.apache.org From: nd@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20060706200514.3BD591A981A@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: nd Date: Thu Jul 6 13:05:12 2006 New Revision: 419688 URL: http://svn.apache.org/viewvc?rev=419688&view=rev Log: fixup properties Modified: httpd/httpd/trunk/docs/manual/mod/mod_aspdotnet.xml (contents, props changed) httpd/httpd/trunk/docs/manual/rewrite/flags.html (contents, props changed) httpd/httpd/trunk/docs/manual/rewrite/flags.html.en (contents, props changed) httpd/httpd/trunk/docs/manual/rewrite/flags.xml (contents, props changed) httpd/httpd/trunk/docs/manual/rewrite/flags.xml.meta (props changed) Modified: httpd/httpd/trunk/docs/manual/mod/mod_aspdotnet.xml URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_aspdotnet.xml?rev=419688&r1=419687&r2=419688&view=diff ============================================================================== --- httpd/httpd/trunk/docs/manual/mod/mod_aspdotnet.xml (original) +++ httpd/httpd/trunk/docs/manual/mod/mod_aspdotnet.xml Thu Jul 6 13:05:12 2006 @@ -1,7 +1,7 @@ - + -Apache mod_rewrite Flags - Apache HTTP Server - - - - - -
<-
-

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.

-
- -
top
-
-

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.

- -
top
-
-

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 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.

+
+ +
top
+
+

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.

+ +
top
+
+

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 

+
Propchange: httpd/httpd/trunk/docs/manual/rewrite/flags.html.en ------------------------------------------------------------------------------ svn:eol-style = native Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.xml URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.xml?rev=419688&r1=419687&r2=419688&view=diff ============================================================================== --- httpd/httpd/trunk/docs/manual/rewrite/flags.xml (original) +++ httpd/httpd/trunk/docs/manual/rewrite/flags.xml Thu Jul 6 13:05:12 2006 @@ -1,7 +1,7 @@ - +