You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2011/01/26 04:31:00 UTC

svn commit: r1063591 - /httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en

Author: covener
Date: Wed Jan 26 03:31:00 2011
New Revision: 1063591

URL: http://svn.apache.org/viewvc?rev=1063591&view=rev
Log:
xforms

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en?rev=1063591&r1=1063590&r2=1063591&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en Wed Jan 26 03:31:00 2011
@@ -354,8 +354,14 @@ Result:
                 MIME-headers, C variables of the Apache server or
                 <code>struct tm</code> fields of the Unix system.
                 Most are documented elsewhere in the Manual or in
-                the CGI specification. Those that are special to
-                mod_rewrite include those below.</p>
+                the CGI specification.</p>
+
+                <p>SERVER_NAME and SERVER_PORT depend on the values of 
+                <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> and
+                <code class="directive"><a href="../mod/core.html#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code>
+                respectively.</p>
+
+                <p>Those that are special to mod_rewrite include those below.</p>
 	<div class="note">
                 <dl>
                   <dt><code>IS_SUBREQ</code></dt>
@@ -1109,7 +1115,7 @@ later</td></tr>
 
       <p><a id="patterns" name="patterns"><em>Pattern</em></a> is
       a perl compatible <a id="regexp" name="regexp">regular
-      expression</a>. On the first RewriteRule it is applied to the (%-encoded)
+      expression</a>. On the first RewriteRule it is applied to the (%-decoded)
       <a href="./directive-dict.html#Syntax">URL-path</a> of the request;
       subsequent patterns are applied to the output of the last matched
       RewriteRule.</p>