You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sf...@apache.org on 2011/10/01 22:57:49 UTC
svn commit: r1178089 [6/12] - in /httpd/httpd/trunk/docs/manual: ./
developer/ howto/ misc/ mod/ platform/ programs/ rewrite/ ssl/ vhosts/
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.html.en Sat Oct 1 20:57:36 2011
@@ -32,7 +32,7 @@
<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in version 2.1 and later</td></tr></table>
<h3>Summary</h3>
- <p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. It provides support for the
+ <p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. It provides support for the
<code>Apache JServ Protocol version 1.3</code> (hereafter
<em>AJP13</em>).</p>
@@ -64,8 +64,8 @@
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="env" id="env">Environment Variables</a></h2>
- <p>Environment variables whose names have the prefix <code>AJP_</code>
- are forwarded to the origin server as AJP request attributes
+ <p>Environment variables whose names have the prefix <code>AJP_</code>
+ are forwarded to the origin server as AJP request attributes
(with the AJP_ prefix removed from the name of the key).</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
@@ -309,7 +309,7 @@ AJP13_FORWARD_REQUEST :=
</pre></div>
<p>The <code>request_headers</code> have the following structure:
</p><div class="example"><pre>
-req_header_name :=
+req_header_name :=
sc_req_header_name | (string) [see below for how this is parsed]
sc_req_header_name := 0xA0xx (integer)
@@ -365,7 +365,7 @@ attribute_value := (string)
<tr><td>BASELINE_CONTROL</td><td>26</td></tr>
<tr><td>MKACTIVITY</td><td>27</td></tr>
</table>
- <p>Later version of ajp13, will transport
+ <p>Later version of ajp13, will transport
additional methods, even if they are not in this list.</p>
<h3>protocol, req_uri, remote_addr, remote_host, server_name,
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml.ja
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml.ja?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml.ja [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml.ja [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 669473:1031731 (outdated) -->
+<!-- English Revision: 669473:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en Sat Oct 1 20:57:36 2011
@@ -76,7 +76,7 @@
<p>At present, there are 3 load balancer scheduler algorithms available
for use: Request Counting, Weighted Traffic Counting and Pending Request
Counting. These are controlled via the <code>lbmethod</code> value of
- the Balancer definition. See the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code>
+ the Balancer definition. See the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code>
directive for more information, especially regarding how to
configure the Balancer and BalancerMembers.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
@@ -147,14 +147,14 @@
<dt><var><a name="balancer_session_route" id="balancer_session_route">BALANCER_SESSION_ROUTE</a></var></dt>
<dd>
- <p>This is assigned the <var>route</var> parsed from the current
+ <p>This is assigned the <var>route</var> parsed from the current
request.</p>
</dd>
<dt><var><a name="balancer_name" id="balancer_name">BALANCER_NAME</a></var></dt>
<dd>
- <p>This is assigned the name of the balancer used for the current
+ <p>This is assigned the name of the balancer used for the current
request. The value is something like <code>balancer://foo</code>.</p>
</dd>
@@ -168,7 +168,7 @@
<dt><var><a name="balancer_worker_route" id="balancer_worker_route">BALANCER_WORKER_ROUTE</a></var></dt>
<dd>
- <p>This is assigned the <var>route</var> of the worker that will be
+ <p>This is assigned the <var>route</var> of the worker that will be
used for the current request.</p>
</dd>
@@ -187,7 +187,7 @@
<div class="section">
<h2><a name="balancer_manager" id="balancer_manager">Enabling Balancer Manager Support</a></h2>
- <p>This module <em>requires</em> the service of
+ <p>This module <em>requires</em> the service of
<code class="module"><a href="../mod/mod_status.html">mod_status</a></code>.
Balancer manager enables dynamic update of balancer
members. You can use balancer manager to change the balance
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml.ja
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml.ja?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml.ja [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml.ja [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 395228:1058629 (outdated) -->
+<!-- English Revision: 395228:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_express.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_express.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_express.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_express.html.en Sat Oct 1 20:57:36 2011
@@ -39,7 +39,7 @@
dynamic growth, but is intended to handle much, much
larger numbers of backends. It is ideally suited as a
front-end HTTP switch.</p>
-
+
<p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>.</p>
<div class="warning"><h3>Warning</h3>
@@ -100,7 +100,7 @@
<div class="note"><h3>Note</h3>
<p>The file is constructed from a plain text file format using
- the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
+ the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
utility.</p>
<div class="example"><h3>ProxyExpress map file</h3><p><code>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en Sat Oct 1 20:57:36 2011
@@ -31,7 +31,7 @@
<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in version 2.3 and later</td></tr></table>
<h3>Summary</h3>
- <p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. It provides support for the
+ <p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. It provides support for the
<a href="http://www.fastcgi.com/">FastCGI</a> protocol.</p>
<p>Thus, in order to get the ability of handling the <code>FastCGI</code>
@@ -39,7 +39,7 @@
<code class="module"><a href="../mod/mod_proxy_fcgi.html">mod_proxy_fcgi</a></code> have to be present in the server.</p>
<p>Unlike <a href="http://httpd.apache.org/mod_fcgid/">mod_fcgid</a>
- and <a href="http://www.fastcgi.com/">mod_fastcgi</a>,
+ and <a href="http://www.fastcgi.com/">mod_fastcgi</a>,
<code class="module"><a href="../mod/mod_proxy_fcgi.html">mod_proxy_fcgi</a></code> has no provision for starting the
application process; <code class="program"><a href="../programs/fcgistarter.html">fcgistarter</a></code> is provided for
that purpose.</p>
@@ -73,10 +73,10 @@
</code></p></div>
<p>This application should be able to handle multiple concurrent
- connections. <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> enables connection reuse by
+ connections. <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> enables connection reuse by
default, so after a request has been completed the connection will be
held open by that httpd child process and won't be reused until that
- httpd process routes another request to the application. If the
+ httpd process routes another request to the application. If the
FastCGI application is unable to handle enough concurrent connections
from httpd, requests can block waiting for the application to close
an existing connection. One way to resolve this is to disable connection
@@ -88,7 +88,7 @@
</code></p></div>
<p>The balanced gateway needs <code class="module"><a href="../mod/mod_proxy_balancer.html">mod_proxy_balancer</a></code> and
- at least one load balancer algorithm module, such as
+ at least one load balancer algorithm module, such as
<code class="module"><a href="../mod/mod_lbmethod_byrequests.html">mod_lbmethod_byrequests</a></code>, in addition to the proxy
modules listed above. <code class="module"><a href="../mod/mod_lbmethod_byrequests.html">mod_lbmethod_byrequests</a></code> is the
default, and will be used for this example configuration.</p>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_fdpass.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_fdpass.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_fdpass.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_fdpass.html.en Sat Oct 1 20:57:36 2011
@@ -34,19 +34,19 @@
<p>This module <em>requires</em> the service of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. It provides support for the passing the socket of the
client to another process.</p>
- <p><code>mod_proxy_fdpass</code> uses the ability of AF_UNIX domain
- sockets to <a href="http://www.freebsd.org/cgi/man.cgi?query=recv">pass an
+ <p><code>mod_proxy_fdpass</code> uses the ability of AF_UNIX domain
+ sockets to <a href="http://www.freebsd.org/cgi/man.cgi?query=recv">pass an
open file descriptor</a> to allow another process to finish handling a request.
</p>
- <p>The module has a <code>proxy_fdpass_flusher</code> provider interface,
+ <p>The module has a <code>proxy_fdpass_flusher</code> provider interface,
which allows another module to optionally send the response headers, or even
the start of the response body. The default flush provider disables keep-alive,
and sends the response headers, letting the external process just send a
response body.</p>
- <p>At this time the only data passed to the external process is the client
- socket. To receive a client socket, call recvfrom with an allocated
+ <p>At this time the only data passed to the external process is the client
+ socket. To receive a client socket, call recvfrom with an allocated
<a href="http://www.kernel.org/doc/man-pages/online/pages/man3/cmsg.3.html"><code>struct cmsghdr</code></a>. Future versions of this module may include
more data after the client socket, but this is not implemented at this time.
</p>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.html.en Sat Oct 1 20:57:36 2011
@@ -69,7 +69,7 @@
</code></p></div>
<p>The balanced gateway needs <code class="module"><a href="../mod/mod_proxy_balancer.html">mod_proxy_balancer</a></code> and
- at least one load balancer algorithm module, such as
+ at least one load balancer algorithm module, such as
<code class="module"><a href="../mod/mod_lbmethod_byrequests.html">mod_lbmethod_byrequests</a></code>, in addition to the proxy
modules listed above. <code class="module"><a href="../mod/mod_lbmethod_byrequests.html">mod_lbmethod_byrequests</a></code> is the
default, and will be used for this example configuration.</p>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_ratelimit.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_ratelimit.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_ratelimit.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_ratelimit.html.en Sat Oct 1 20:57:36 2011
@@ -30,8 +30,8 @@
<h3>Summary</h3>
-<p>Provides a <code>rate_limit</code> filter to limit client bandwidth.
-The connection speed to be simulated is specified, in kb/s, using the environment
+<p>Provides a <code>rate_limit</code> filter to limit client bandwidth.
+The connection speed to be simulated is specified, in kb/s, using the environment
variable <code>rate-limit</code>.</p>
<div class="example"><h3>Example Configuration</h3><p><code>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_remoteip.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_remoteip.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_remoteip.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_remoteip.html.en Sat Oct 1 20:57:36 2011
@@ -24,8 +24,8 @@
<p><span>Available Languages: </span><a href="../en/mod/mod_remoteip.html" title="English"> en </a> |
<a href="../fr/mod/mod_remoteip.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
</div>
-<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Replaces the apparent client remote IP address and hostname
-for the request with the IP address list presented by a proxies or a load
+<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Replaces the apparent client remote IP address and hostname
+for the request with the IP address list presented by a proxies or a load
balancer via the request headers.
</td></tr>
<tr><th><a href="module-dict.html#Status">Status:</a></th><td>Base</td></tr>
@@ -33,12 +33,12 @@ balancer via the request headers.
<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_remoteip.c</td></tr></table>
<h3>Summary</h3>
- <p>This module is used to treat the remote host which initiated the
+ <p>This module is used to treat the remote host which initiated the
request as the originating remote host as identified by httpd for the
purposes of authorization and logging, even where that remote host is
behind a load balancer, front end server, or proxy server.</p>
- <p>The module replaces the apparent remote (client) IP/hostname for
+ <p>The module replaces the apparent remote (client) IP/hostname for
the request with the IP address reported in the request header
configured with the <code class="directive">RemoteIPHeader</code> directive.</p>
@@ -48,8 +48,8 @@ balancer via the request headers.
and <code class="directive"><a href="../mod/mod_authz_host.html#require ip"><Require ip></a></code>,
is reported by <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>, and is recorded by
<code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code> <code>%a</code> and <code>%h</code>
- directives. It also determines the machine probed for an inetd
- identity by <code class="module"><a href="../mod/mod_ident.html">mod_ident</a></code> based on the
+ directives. It also determines the machine probed for an inetd
+ identity by <code class="module"><a href="../mod/mod_ident.html">mod_ident</a></code> based on the
<code class="directive"><a href="../mod/mod_ident.html#identitycheck">IdentityCheck</a></code> configuration.</p>
<div class="warning">It is critical to only enable this behavior from
@@ -81,19 +81,19 @@ balancer via the request headers.
<h2><a name="processing" id="processing">Remote IP Processing</a></h2>
<p>Apache identifies the client with the connection's remote_ip value,
- and the connection remote_host and remote_logname are derived from this
- value. These fields play a role in authentication, authorization and
+ and the connection remote_host and remote_logname are derived from this
+ value. These fields play a role in authentication, authorization and
logging and other purposes by other loadable modules.</p>
<p>mod_remoteip replaces the true remote_ip with the advertised remote_ip as
provided by a proxy, for every evaluation of the client that occurs in the
- server, and resets the remote_host and remote_logname values to trigger a
+ server, and resets the remote_host and remote_logname values to trigger a
fresh dns or ident query of the remote IP address.</p>
- <p>When multiple, comma delimited remote IP addresses are listed in the
+ <p>When multiple, comma delimited remote IP addresses are listed in the
header value, they are processed in Right-to-Left order. Processing
halts when a given remote IP address is not trusted to present the
- preceeding IP address. The header field is updated to this remaining
+ preceeding IP address. The header field is updated to this remaining
list of unconfirmed IP addresses, or if all IP addresses were trusted,
this header is removed from the request altogether.</p>
@@ -112,7 +112,7 @@ balancer via the request headers.
All internal addresses 10/8, 172.16/12, 192.168/16, 169.254/16 and 127/8
blocks (and IPv6 addresses outside of the public 2000::/3 block) are only
evaluated by mod_remoteip when <code class="directive">RemoteIPInternalProxy</code>
- internal (intranet) proxies are registered.</div>
+ internal (intranet) proxies are registered.</div>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
@@ -124,10 +124,10 @@ balancer via the request headers.
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_remoteip</td></tr>
</table>
- <p>The <code class="directive">RemoteIPHeader</code> directive triggers
+ <p>The <code class="directive">RemoteIPHeader</code> directive triggers
<code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> to treat the value of the specified
<var>header-field</var> header as the client IP address, or list
- of intermediate client IP addresses, subject to further configuration
+ of intermediate client IP addresses, subject to further configuration
of the <code class="directive">RemoteIPInternalProxy</code> and
<code class="directive">RemoteIPTrustedProxy</code> directives. Unless these
other directives are used, <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> will trust all
@@ -155,7 +155,7 @@ balancer via the request headers.
or more addresses (or address blocks) to trust as presenting a valid
RemoteIPHeader value of the client IP. Unlike the
<code class="directive">RemoteIPTrustedProxy</code> directive, any IP address
- presented in this header, including private intranet addresses, are
+ presented in this header, including private intranet addresses, are
trusted when passed from these proxies.</p>
<div class="example"><h3>Internal (Load Balancer) Example</h3><p><code>
@@ -207,7 +207,7 @@ balancer via the request headers.
a header into which <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> will collect a list of
all of the intermediate client IP addresses trusted to resolve the actual
remote IP. Note that intermediate <code class="directive">RemoteIPTrustedProxy</code>
- addresses are recorded in this header, while any intermediate
+ addresses are recorded in this header, while any intermediate
<code class="directive">RemoteIPInternalProxy</code> addresses are discarded.</p>
<div class="example"><h3>Example</h3><p><code>
@@ -228,10 +228,10 @@ balancer via the request headers.
<p>The <code class="directive">RemoteIPTrustedProxy</code> directive adds one
or more addresses (or address blocks) to trust as presenting a valid
RemoteIPHeader value of the client IP. Unlike the
- <code class="directive">RemoteIPInternalProxy</code> directive, any intranet
+ <code class="directive">RemoteIPInternalProxy</code> directive, any intranet
or private IP address reported by such proxies, including the 10/8, 172.16/12,
192.168/16, 169.254/16 and 127/8 blocks (or outside of the IPv6 public
- 2000::/3 block) are not trusted as the remote IP, and are left in the
+ 2000::/3 block) are not trusted as the remote IP, and are left in the
<code class="directive">RemoteIPHeader</code> header's value.</p>
<div class="example"><h3>Trusted (Load Balancer) Example</h3><p><code>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.en Sat Oct 1 20:57:36 2011
@@ -31,21 +31,21 @@ URLs on the fly</td></tr>
<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_rewrite.c</td></tr></table>
<h3>Summary</h3>
- <p>The <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> module uses a rule-based rewriting
+ <p>The <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> module uses a rule-based rewriting
engine, based on a regular-expression parser, to rewrite requested URLs on
- the fly. By default, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> maps a URL to a filesystem
+ the fly. By default, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> maps a URL to a filesystem
path. However, it can also be used to redirect one URL to another URL, or
to invoke an internal proxy fetch.</p>
- <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> provides a flexible and powerful way to
- manipulate URLs using an unlimited number of rules. Each rule can have an
+ <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> provides a flexible and powerful way to
+ manipulate URLs using an unlimited number of rules. Each rule can have an
unlimited number of attached rule conditions, to allow you to rewrite URL
- based on server variables, environment variables, HTTP headers, or time
+ based on server variables, environment variables, HTTP headers, or time
stamps.</p>
<p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> operates on the full URL path, including the
- path-info section. A rewrite rule can be invoked in
- <code>httpd.conf</code> or in <code>.htaccess</code>. The path generated
- by a rewrite rule can include a query string, or can lead to internal
- sub-processing, external request redirection, or internal proxy
+ path-info section. A rewrite rule can be invoked in
+ <code>httpd.conf</code> or in <code>.htaccess</code>. The path generated
+ by a rewrite rule can include a query string, or can lead to internal
+ sub-processing, external request redirection, or internal proxy
throughput.</p>
<p>Further details, discussion, and examples, are provided in the
@@ -117,13 +117,13 @@ URLs on the fly</td></tr>
that result in the substitution of a relative path.
When you use a <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
in a <code>.htaccess</code> file, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> strips off
- the local directory prefix before processing, then rewrites the rest of
+ the local directory prefix before processing, then rewrites the rest of
the URL. When the rewrite is completed, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
automatically adds the local directory prefix (or the
- <code class="directive">RewriteBase</code> when set) back on to the substitution
+ <code class="directive">RewriteBase</code> when set) back on to the substitution
before handing it back to the core of the server as if it were the original
URL.</p>
-
+
<p>This directive is <em>required</em> for per-directory rewrites whose context
is a directory made available via the <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>
directive, when the substitution uses a relative path.</p>
@@ -133,9 +133,9 @@ URLs on the fly</td></tr>
you must use <code class="directive">RewriteBase</code> in every
<code>.htaccess</code> file where you want to use <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives.</p>
- <p>The example below demonstrates how to map
- http://example.com/myapp/index.html to
- /home/www/example/newsite.html, in a <code>.htaccess</code> file. This
+ <p>The example below demonstrates how to map
+ http://example.com/myapp/index.html to
+ /home/www/example/newsite.html, in a <code>.htaccess</code> file. This
assumes that the content available at
http://example.com/ is on disk at /home/www/example/</p>
<div class="example"><pre>
@@ -279,7 +279,7 @@ RewriteRule ^index\.html$ newsite.html
Most are documented elsewhere in the Manual or in
the CGI specification.</p>
- <p>SERVER_NAME and SERVER_PORT depend on the values of
+ <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>
@@ -312,7 +312,7 @@ RewriteRule ^index\.html$ newsite.html
browser to the server (e.g., "<code>GET
/index.html HTTP/1.1</code>"). This does not
include any additional headers sent by the
- browser. This value has not been unescaped
+ browser. This value has not been unescaped
(decoded), unlike most other variables below.</dd>
<dt><code>REQUEST_URI</code></dt>
@@ -326,9 +326,9 @@ RewriteRule ^index\.html$ newsite.html
<dd>The full local filesystem path to the file or
script matching the request, if this has already
- been determined by the server at the time
- <code>REQUEST_FILENAME</code> is referenced. Otherwise,
- such as when used in virtual host context, the same
+ been determined by the server at the time
+ <code>REQUEST_FILENAME</code> is referenced. Otherwise,
+ such as when used in virtual host context, the same
value as <code>REQUEST_URI</code>.</dd>
<dt><code>HTTPS</code></dt>
@@ -512,7 +512,7 @@ RewriteRule ^index\.html$ newsite.html
numerically compared to the <em>CondPattern</em>. True if
the <em>TestString</em> is numerically greater than or equal
to the <em>CondPattern</em>.</li>
-
+
<li>'<strong>-gt</strong>' (is numerically
<strong>g</strong>reater <strong>t</strong>han)<br />
The <em>TestString</em> is treated as an integer, and is
@@ -528,7 +528,7 @@ RewriteRule ^index\.html$ newsite.html
to the <em>CondPattern</em>. Avoid confusion with the
<strong>-l</strong> by using the <strong>-L</strong> or
<strong>-h</strong> variant.</li>
-
+
<li>'<strong>-lt</strong>' (is numerically
<strong>l</strong>ess <strong>t</strong>han)<br />
The <em>TestString</em> is treated as an integer, and is
@@ -800,7 +800,7 @@ Apache HTTP Server 2.0.41 and later</td>
<dt>dbm</dt>
<dd>Looks up an entry in a dbm file containing name, value
pairs. Hash is constructed from a plain text file format using
- the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
+ the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
utility. (<a href="../rewrite/rewritemap.html#dbm">Details ...</a>)</dd>
<dt>int</dt>
@@ -842,7 +842,7 @@ later</td></tr>
<dl>
<dt><code>Inherit</code></dt>
<dd>
-
+
<p>This forces the current configuration to inherit the
configuration of the parent. In per-virtual-server context,
this means that the maps, conditions and rules of the main
@@ -857,7 +857,7 @@ later</td></tr>
of local rules - has no influence on this behavior. If local
rules forced the rewriting to stop, the inherited rules won't
be processed.</p>
-
+
<div class="warning">
Rules inherited from the parent scope are applied
<strong>after</strong> rules specified in the child scope.
@@ -867,10 +867,10 @@ later</td></tr>
<dt><code>InheritBefore</code></dt>
<dd>
<p> Like <code>Inherit</code> above, but the rules from the parent scope
- are applied <strong>before</strong> rules specified in the child scope.
+ are applied <strong>before</strong> rules specified in the child scope.
Available in Apache HTTP Server 2.3.10 and later.</p>
</dd>
-
+
</dl>
@@ -900,16 +900,16 @@ later</td></tr>
RewriteRule.</p>
<div class="note"><h3>What is matched?</h3>
- <p>In <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> context,
+ <p>In <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> context,
The <em>Pattern</em> will initially be matched against the part of the
URL after the hostname and port, and before the query string (e.g. "/app1/index.html").</p>
<p>In <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> and htaccess context,
- the <em>Pattern</em> will initially be matched against the
+ the <em>Pattern</em> will initially be matched against the
<em>filesystem</em> path, after removing the prefix that lead the server
- to the current <code class="directive">RewriteRule</code> (e.g. "app1/index.html"
+ to the current <code class="directive">RewriteRule</code> (e.g. "app1/index.html"
or "index.html" depending on where the directives are defined).</p>
-
+
<p>If you wish to match against the hostname, port, or query string, use a
<code class="directive"><a href="#rewritecond">RewriteCond</a></code> with the
<code>%{HTTP_HOST}</code>, <code>%{SERVER_PORT}</code>, or
@@ -933,12 +933,12 @@ restriction is required for security rea
per-directory prefix (which always is the same for a specific
directory) is automatically <em>removed</em> for the RewriteRule pattern matching
and automatically <em>added</em> after any relative (not starting with a
-slash or protocol name) substitution encounters the end of a rule set.
-See the <code class="directive"><a href="#rewritebase">RewriteBase</a></code>
-directive for more information regarding what prefix will be added back to
+slash or protocol name) substitution encounters the end of a rule set.
+See the <code class="directive"><a href="#rewritebase">RewriteBase</a></code>
+directive for more information regarding what prefix will be added back to
relative substutions.</li>
-<li> If you wish to match against the full URL-path in a per-directory
+<li> If you wish to match against the full URL-path in a per-directory
(htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
a <code class="directive">RewriteCond</code>.</li>
@@ -1088,14 +1088,14 @@ cannot use <code>$N</code> in the substi
</tr>
<tr>
<td>cookie|CO=<em>NAME</em>:<em>VAL</em></td>
- <td>Sets a cookie in the client browser. Full syntax is:
+ <td>Sets a cookie in the client browser. Full syntax is:
CO=<em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>[:<em>secure</em>[:<em>httponly</em>]]]] <em><a href="../rewrite/flags.html#flag_co">details ...</a></em>
</td>
</tr>
<tr>
<td>discardpath|DPI</td>
<td>Causes the PATH_INFO portion of the rewritten URI to be
- discarded. <em><a href="../rewrite/flags.html#flag_dpi">details
+ discarded. <em><a href="../rewrite/flags.html#flag_dpi">details
...</a></em></td>
</tr>
<tr>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.fr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.fr?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.fr (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_rewrite.html.fr Sat Oct 1 20:57:36 2011
@@ -155,7 +155,7 @@ répertoire</td></tr>
<code>.htaccess</code>. On suppose que le contenu disponible à
http://example.com/ se situe sur le disque à
/home/www/exemple/.</p>
-
+
<div class="example"><pre>
RewriteEngine On
# Le chemin URL utilisé pour arriver dans ce contexte, et non le chemin
@@ -189,7 +189,7 @@ la réécriture soit effectuée
<p><em>TestString</em> est une chaîne qui peut contenir les
extensions suivantes en plus du texte simple :</p>
-
+
<ul>
<li>
<strong>références arrières de règle de réécriture</strong> :
@@ -291,7 +291,7 @@ la réécriture soit effectuée
</td>
</tr>
</table>
-
+
<p>Ces variables correspondent toutes aux en-têtes MIME
HTTP de mêmes noms, au variables C du serveur HTTP Apache, ou
aux champs <code>struct tm</code> du système Unix. La
@@ -300,7 +300,7 @@ la réécriture soit effectuée
<p>SERVER_NAME et SERVER_PORT dépendent respectivement
des valeurs des directives <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> et <code class="directive"><a href="../mod/core.html#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code>.</p>
-
+
<p>Parmi les variables
spécifiques à mod_rewrite, ou trouve les suivantes :</p>
<div class="note">
@@ -420,7 +420,7 @@ la réécriture soit effectuée
chargé, cette variable contiendra toujours une chaîne vide.
Exemple : <code>%{SSL:SSL_CIPHER_USEKEYSIZE}</code> pourra
contenir la valeur <code>128</code>.</li>
-
+
<li>
On peut utiliser <code>%{HTTP:en-tête}</code>, où
<em>en-tête</em> peut correspondre à tout nom d'en-tête MIME
@@ -465,8 +465,8 @@ la réécriture soit effectuée
déterminer la valeur finale de <em>variable</em>. La plupart du
temps, elle est identique à LA-U (voir ci-dessus).</li>
</ol>
-
-
+
+
<p><em>expression de comparaison</em> est une expression
rationnelle qui est appliquée à l'instance actuelle de
<em>chaîne de test</em>. <em>chaîne de test</em> est d'abord
@@ -551,7 +551,7 @@ la réécriture soit effectuée
comparaison</em>. Vrai si <em>chaîne de test</em> est
numériquement
supérieure ou égale à <em>expression de comparaison</em>.</li>
-
+
<li>'<strong>-gt</strong>' (est numériquement supérieur à)<br />
La <em>chaîne de test</em> est considérée comme un entier,
et est comparée numériquement à l'<em>expression de
@@ -569,7 +569,7 @@ la réécriture soit effectuée
Attention à la confusion avec le drapeau <strong>-l</strong>
en utilisant la variante the <strong>-L</strong> ou
<strong>-h</strong>.</li>
-
+
<li>'<strong>-lt</strong>' (est numériquement inférieur à)<br />
La <em>chaîne de test</em> est considérée comme un entier,
et est comparée numériquement à l'<em>expression de
@@ -880,7 +880,7 @@ bases de données depuis la version 2.0.
<dd>Une commande SQL SELECT à exécuter pour rechercher la cible
de réécriture (<a href="../rewrite/rewritemap.html#int">Détails
...</a>).</dd>
- </dl>
+ </dl>
<p>Vous trouverez plus de détails et de nombreux exemples dans le <a href="../rewrite/rewritemap.html">RewriteMap HowTo</a>.</p>
@@ -970,7 +970,7 @@ la version version 2.1</td></tr>
la dernière règle de réécriture qui a été appliquée.</p>
<div class="note"><h3>Qu'est-ce qui est comparé ?</h3>
-
+
<p>Dans un contexte de serveur virtuel <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code>, le <em>modèle</em> est tout
d'abord comparé à la portion de l'URL située entre le nom d'hôte
éventuellement accompagné du port, et la chaîne de paramètres (par
@@ -982,7 +982,7 @@ la version version 2.1</td></tr>
ayant conduit à la règle <code class="directive">RewriteRule</code> (par
exemple "app1/index.html" ou
"index.html" selon l'endroit où les directives sont définies).</p>
-
+
<p>Si vous souhaitez faire une comparaison sur le nom
d'hôte, le port, ou la chaîne de requête, utilisez une
directive <code class="directive"><a href="#rewritecond">RewriteCond</a></code>
@@ -1194,7 +1194,7 @@ substitution !
</tr>
<tr>
<td>discardpath|DPI</td>
- <td>Supprime la partie PATH_INFO de l'URI réécrit. <em><a href="../rewrite/flags.html#flag_dpi">détails
+ <td>Supprime la partie PATH_INFO de l'URI réécrit. <em><a href="../rewrite/flags.html#flag_dpi">détails
...</a></em></td>
</tr>
<tr>
@@ -1295,7 +1295,7 @@ substitution !
spécifié au fichier cible. <em><a href="../rewrite/flags.html#flag_t">détails ...</a></em></td>
</tr>
</table>
-
+
<div class="note"><h3>Développement du répertoire home</h3>
<p> Quand la chaîne de substitution commence par quelque chose comme
"/~user" (de manière explicite ou par références arrières), mod_rewrite
@@ -1381,7 +1381,7 @@ redondant)</td>
<td>^/somepath(.*) http://otherhost/otherpath$1 [P]</td>
<td>http://otherhost/otherpath/pathinfo via internal proxy</td>
</tr>
-</table>
+</table>
<p><strong>Dans une configuration de niveau répertoire pour
<code>/chemin</code><br />
Modified: httpd/httpd/trunk/docs/manual/mod/mod_session.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session.html.en Sat Oct 1 20:57:36 2011
@@ -42,7 +42,7 @@
interface. Sessions can be used for keeping track of whether a user
has been logged in, or for other per user information that should
be kept available across requests.</p>
-
+
<p>Sessions may be stored on the server, or may be stored on the
browser. Sessions may also be optionally encrypted for added security.
These features are divided into several modules in addition to
@@ -55,7 +55,7 @@
<p>Sessions may be manipulated from other modules that depend on the
session, or the session may be read from and written to using
environment variables and HTTP headers, as appropriate.</p>
-
+
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
@@ -87,10 +87,10 @@
<h2><a name="whatisasession" id="whatisasession">What is a session?</a></h2>
<p>At the core of the session interface is a table of key and value pairs
that are made accessible across browser requests.</p>
-
+
<p>These pairs can be set to any valid string, as needed by the
application making use of the session.</p>
-
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="whocanuseasession" id="whocanuseasession">Who can use a session?</a></h2>
@@ -107,17 +107,17 @@
<p>Apache can be configured to keep track of per user sessions stored
on a particular server or group of servers. This functionality is
similar to the sessions available in typical application servers.</p>
-
+
<p>If configured, sessions are tracked through the use of a session ID that
is stored inside a cookie, or extracted from the parameters embedded
within the URL query string, as found in a typical GET request.</p>
-
+
<p>As the contents of the session are stored exclusively on the server,
there is an expectation of privacy of the contents of the session. This
does have performance and resource implications should a large number
of sessions be present, or where a large number of webservers have to
share sessions with one another.</p>
-
+
<p>The <code class="module"><a href="../mod/mod_session_dbd.html">mod_session_dbd</a></code> module allows the storage of user
sessions within a SQL database via <code class="module"><a href="../mod/mod_dbd.html">mod_dbd</a></code>.</p>
@@ -127,11 +127,11 @@
<p>Where keeping track of a session on a server is too resource
intensive or inconvenient, the option exists to store the contents
of the session within a cookie on the client browser instead.</p>
-
+
<p>This has the advantage that minimal resources are required on the
server to keep track of sessions, and multiple servers within a server
farm have no need to share session information.</p>
-
+
<p>The contents of the session however are exposed to the client, with a
corresponding risk of a loss of privacy. The
<code class="module"><a href="../mod/mod_session_crypto.html">mod_session_crypto</a></code> module can be configured to encrypt the
@@ -143,11 +143,11 @@
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="basicexamples" id="basicexamples">Basic Examples</a></h2>
-
+
<p>Creating a session is as simple as turning the session on, and deciding
where the session will be stored. In this example, the session will be
stored on the browser, in a cookie called <code>session</code>.</p>
-
+
<div class="example"><h3>Browser based session</h3><p><code>
Session On<br />
SessionCookieName session path=/<br />
@@ -157,7 +157,7 @@
following example shows how values can be injected into the session through
the use of a predetermined HTTP response header called
<code>X-Replace-Session</code>.</p>
-
+
<div class="example"><h3>Writing to a session</h3><p><code>
Session On<br />
SessionCookieName session path=/<br />
@@ -167,7 +167,7 @@
<p>The header should contain name value pairs expressed in the same format
as a query string in a URL, as in the example below. Setting a key to the
empty string has the effect of removing that key from the session.</p>
-
+
<div class="example"><h3>CGI to write to a session</h3><p><code>
#!/bin/bash<br />
echo "Content-Type: text/plain"<br />
@@ -180,7 +180,7 @@
environment variable. By default, the session is kept private, so this
has to be explicitly turned on with the
<code class="directive"><a href="#sessionenv">SessionEnv</a></code> directive.</p>
-
+
<div class="example"><h3>Read from a session</h3><p><code>
Session On<br />
SessionEnv On<br />
@@ -194,32 +194,32 @@
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="sessionprivacy" id="sessionprivacy">Session Privacy</a></h2>
-
+
<p>Using the "show cookies" feature of your browser, you would have seen
a clear text representation of the session. This could potentially be a
problem should the end user need to be kept unaware of the contents of
the session, or where a third party could gain unauthorised access to the
data within the session.</p>
-
+
<p>The contents of the session can be optionally encrypted before being
placed on the browser using the <code class="module"><a href="../mod/mod_session_crypto.html">mod_session_crypto</a></code>
module.</p>
-
+
<div class="example"><h3>Browser based encrypted session</h3><p><code>
Session On<br />
SessionCryptoPassphrase secret<br />
SessionCookieName session path=/<br />
</code></p></div>
-
+
<p>The session will be automatically decrypted on load, and encrypted on
save by Apache, the underlying application using the session need have
no knowledge that encryption is taking place.</p>
-
+
<p>Sessions stored on the server rather than on the browser can also be
encrypted as needed, offering privacy where potentially sensitive
information is being shared between webservers in a server farm using
the <code class="module"><a href="../mod/mod_session_dbd.html">mod_session_dbd</a></code> module.</p>
-
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="cookieprivacy" id="cookieprivacy">Cookie Privacy</a></h2>
@@ -228,7 +228,7 @@
ability to restrict cookie transport to SSL protected pages only, or
to prevent browser based javascript from gaining access to the contents
of the cookie.</p>
-
+
<div class="warning"><h3>Warning</h3>
<p>Some of the HTTP cookie privacy features are either non-standard, or
are not implemented consistently across browsers. The session modules
@@ -241,13 +241,13 @@
<p>Standard cookie parameters can be specified after the name of the cookie,
as in the example below.</p>
-
+
<div class="example"><h3>Setting cookie parameters</h3><p><code>
Session On<br />
SessionCryptoPassphrase secret<br />
SessionCookieName session path=/private;domain=example.com;httponly;secure;<br />
</code></p></div>
-
+
<p>In cases where the Apache server forms the frontend for backend origin servers,
it is possible to have the session cookies removed from the incoming HTTP headers using
the <code class="directive"><a href="../mod/mod_session_cookie.html#sessioncookieremove">SessionCookieRemove</a></code> directive.
@@ -274,7 +274,7 @@
AuthName realm<br />
...<br />
</code></p></div>
-
+
<p>See the <code class="module"><a href="../mod/mod_auth_form.html">mod_auth_form</a></code> module for documentation and complete
examples.</p>
@@ -308,7 +308,7 @@
<p>If set to <var>On</var>, the <code class="directive">SessionEnv</code> directive
causes the contents of the session to be written to a CGI environment
variable called <var>HTTP_SESSION</var>.</p>
-
+
<p>The string is written in the URL query format, for example:</p>
<div class="example"><p><code>
@@ -356,13 +356,13 @@
<p>The <code class="directive">SessionHeader</code> directive defines the name of an
HTTP response header which, if present, will be parsed and written to the
current session.</p>
-
+
<p>The header value is expected to be in the URL query format, for example:</p>
<div class="example"><p><code>
<code>key1=foo&key2=&key3=bar</code>
</code></p></div>
-
+
<p>Where a key is set to the empty string, that key will be removed from the
session.</p>
@@ -383,7 +383,7 @@
website more efficient, by targeting a more precise URL space for which
a session should be maintained. By default, all URLs within the directory
or location are included in the session.</p>
-
+
<div class="warning"><h3>Warning</h3>
<p>This directive has a similar purpose to the <var>path</var> attribute
in HTTP cookies, but should not be confused with this attribute. This
@@ -408,7 +408,7 @@
the session, the session will time out and be removed. Where a session is
used to stored user login details, this has the effect of logging the user
out automatically after the given time.</p>
-
+
<p>Setting the maxage to zero disables session expiry.</p>
</div>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.html.en Sat Oct 1 20:57:36 2011
@@ -40,19 +40,19 @@
<p>This submodule of <code class="module"><a href="../mod/mod_session.html">mod_session</a></code> provides support for the
storage of user sessions on the remote browser within HTTP cookies.</p>
-
+
<p>Using cookies to store a session removes the need for the server or
a group of servers to store the session locally, or collaborate to share
a session, and can be useful for high traffic environments where a
server based session might be too resource intensive.</p>
-
+
<p>If session privacy is required, the <code class="module"><a href="../mod/mod_session_crypto.html">mod_session_crypto</a></code>
module can be used to encrypt the contents of the session before writing
the session to the client.</p>
-
+
<p>For more details on the session interface, see the documentation for
the <code class="module"><a href="../mod/mod_session.html">mod_session</a></code> module.</p>
-
+
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
@@ -72,19 +72,19 @@
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="basicexamples" id="basicexamples">Basic Examples</a></h2>
-
+
<p>To create a simple session and store it in a cookie called
<var>session</var>, configure the session as follows:</p>
-
+
<div class="example"><h3>Browser based session</h3><p><code>
Session On<br />
SessionCookieName session path=/<br />
</code></p></div>
-
+
<p>For more examples on how the session can be configured to be read
from and written to by a CGI application, see the
<code class="module"><a href="../mod/mod_session.html">mod_session</a></code> examples section.</p>
-
+
<p>For documentation on how the session can be used to store username
and password details, see the <code class="module"><a href="../mod/mod_auth_form.html">mod_auth_form</a></code> module.</p>
@@ -103,12 +103,12 @@
optional attributes of an RFC2109 compliant cookie inside which the session will
be stored. RFC2109 cookies are set using the <code>Set-Cookie</code> HTTP header.
</p>
-
+
<p>An optional list of cookie attributes can be specified, as per the example below.
These attributes are inserted into the cookie as is, and are not interpreted by
Apache. Ensure that your attributes are defined correctly as per the cookie specification.
</p>
-
+
<div class="example"><h3>Cookie with attributes</h3><p><code>
Session On<br />
SessionCookieName session path=/private;domain=example.com;httponly;secure;version=1;<br />
@@ -130,12 +130,12 @@
optional attributes of an RFC2965 compliant cookie inside which the session will
be stored. RFC2965 cookies are set using the <code>Set-Cookie2</code> HTTP header.
</p>
-
+
<p>An optional list of cookie attributes can be specified, as per the example below.
These attributes are inserted into the cookie as is, and are not interpreted by
Apache. Ensure that your attributes are defined correctly as per the cookie specification.
</p>
-
+
<div class="example"><h3>Cookie2 with attributes</h3><p><code>
Session On<br />
SessionCookieName2 session path=/private;domain=example.com;httponly;secure;version=1;<br />
@@ -155,7 +155,7 @@
</table>
<p>The <code class="directive">SessionCookieRemove</code> flag controls whether the cookies
containing the session will be removed from the headers during request processing.</p>
-
+
<p>In a reverse proxy situation where the Apache server acts as a server frontend for
a backend origin server, revealing the contents of the session cookie to the backend
could be a potential privacy violation. When set to on, the session cookie will be
Modified: httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.html.en Sat Oct 1 20:57:36 2011
@@ -41,14 +41,14 @@
<p>This submodule of <code class="module"><a href="../mod/mod_session.html">mod_session</a></code> provides support for the
encryption of user sessions before being written to a local database, or
written to a remote browser via an HTTP cookie.</p>
-
+
<p>This can help provide privacy to user sessions where the contents of
the session should be kept private from the user, or where protection is
needed against the effects of cross site scripting attacks.</p>
-
+
<p>For more details on the session interface, see the documentation for
the <code class="module"><a href="../mod/mod_session.html">mod_session</a></code> module.</p>
-
+
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
@@ -67,23 +67,23 @@
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="basicusage" id="basicusage">Basic Usage</a></h2>
-
+
<p>To create a simple encrypted session and store it in a cookie called
<var>session</var>, configure the session as follows:</p>
-
+
<div class="example"><h3>Browser based encrypted session</h3><p><code>
Session On<br />
SessionCookieName session path=/<br />
SessionCryptoPassphrase secret
</code></p></div>
-
+
<p>The session will be encrypted with the given key. Different servers can
be configured to share sessions by ensuring the same encryption key is used
on each server.</p>
-
+
<p>If the encryption key is changed, sessions will be invalidated
automatically.</p>
-
+
<p>For documentation on how the session can be used to store username
and password details, see the <code class="module"><a href="../mod/mod_auth_form.html">mod_auth_form</a></code> module.</p>
@@ -155,7 +155,7 @@
<p>The cipher can be set to <var>3des192</var> or <var>aes256</var> using the
<var>cipher</var> parameter as per the example below. If not set, the cipher defaults
to <var>aes256</var>.</p>
-
+
<div class="example"><h3>Cipher</h3><p><code>
SessionCryptoPassphrase secret cipher=aes256
</code></p></div>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.html.en Sat Oct 1 20:57:36 2011
@@ -49,13 +49,13 @@
<p>SQL based sessions are hidden from the browser, and so offer a measure of
privacy without the need for encryption.</p>
-
+
<p>Different webservers within a server farm may choose to share a database,
and so share sessions with one another.</p>
-
+
<p>For more details on the session interface, see the documentation for
the <code class="module"><a href="../mod/mod_session.html">mod_session</a></code> module.</p>
-
+
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
@@ -88,7 +88,7 @@
<p>Before the <code class="module"><a href="../mod/mod_session_dbd.html">mod_session_dbd</a></code> module can be configured to maintain a
session, the <code class="module"><a href="../mod/mod_dbd.html">mod_dbd</a></code> module must be configured to make the various database queries
available to the server.</p>
-
+
<p>There are four queries required to keep a session maintained, to select an existing session,
to update an existing session, to insert a new session, and to delete an expired or empty
session. These queries are configured as per the example below.</p>
@@ -106,58 +106,58 @@
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="anonymous" id="anonymous">Anonymous Sessions</a></h2>
-
+
<p>Anonymous sessions are keyed against a unique UUID, and stored on the
browser within an HTTP cookie. This method is similar to that used by most
application servers to store session information.</p>
-
+
<p>To create a simple anonymous session and store it in a postgres database
table called <var>apachesession</var>, and save the session ID in a cookie
called <var>session</var>, configure the session as follows:</p>
-
+
<div class="example"><h3>SQL based anonymous session</h3><p><code>
Session On<br />
SessionDBDCookieName session path=/<br />
</code></p></div>
-
+
<p>For more examples on how the session can be configured to be read
from and written to by a CGI application, see the
<code class="module"><a href="../mod/mod_session.html">mod_session</a></code> examples section.</p>
-
+
<p>For documentation on how the session can be used to store username
and password details, see the <code class="module"><a href="../mod/mod_auth_form.html">mod_auth_form</a></code> module.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="peruser" id="peruser">Per User Sessions</a></h2>
-
+
<p>Per user sessions are keyed against the username of a successfully
authenticated user. It offers the most privacy, as no external handle
to the session exists outside of the authenticated realm.</p>
-
+
<p>Per user sessions work within a correctly configured authenticated
environment, be that using basic authentication, digest authentication
or SSL client certificates. Due to the limitations of who came first,
the chicken or the egg, per user sessions cannot be used to store
authentication credentials from a module like
<code class="module"><a href="../mod/mod_auth_form.html">mod_auth_form</a></code>.</p>
-
+
<p>To create a simple per user session and store it in a postgres database
table called <var>apachesession</var>, and with the session keyed to the
userid, configure the session as follows:</p>
-
+
<div class="example"><h3>SQL based per user session</h3><p><code>
Session On<br />
SessionDBDPerUser On<br />
</code></p></div>
-
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="housekeeping" id="housekeeping">Database Housekeeping</a></h2>
<p>Over the course of time, the database can be expected to start accumulating
expired sessions. At this point, the <code class="module"><a href="../mod/mod_session_dbd.html">mod_session_dbd</a></code> module
is not yet able to handle session expiry automatically.</p>
-
+
<div class="warning"><h3>Warning</h3>
<p>The administrator will need to set up an external process via cron to clean
out expired sessions.</p>
@@ -205,12 +205,12 @@
optional attributes of an RFC2965 compliant cookie inside which the session ID will
be stored. RFC2965 cookies are set using the <code>Set-Cookie2</code> HTTP header.
</p>
-
+
<p>An optional list of cookie attributes can be specified, as per the example below.
These attributes are inserted into the cookie as is, and are not interpreted by
Apache. Ensure that your attributes are defined correctly as per the cookie specification.
</p>
-
+
<div class="example"><h3>Cookie2 with attributes</h3><p><code>
Session On<br />
SessionDBDCookieName2 session path=/private;domain=example.com;httponly;secure;version=1;<br />
Modified: httpd/httpd/trunk/docs/manual/mod/mod_setenvif.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_setenvif.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_setenvif.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_setenvif.html.en Sat Oct 1 20:57:36 2011
@@ -83,8 +83,8 @@ on characteristics of the request</td></
<code>User-Agent</code> HTTP request header. The following two
lines have the same effect:</p>
<div class="example"><p><code>
- BrowserMatchNoCase Robot is_a_robot<br />
- SetEnvIfNoCase User-Agent Robot is_a_robot<br />
+ BrowserMatchNoCase Robot is_a_robot<br />
+ SetEnvIfNoCase User-Agent Robot is_a_robot<br />
</code></p></div>
<p>Some additional examples:</p>
@@ -148,7 +148,7 @@ respect to case</td></tr>
<ol>
<li>An HTTP request header field (see <a href="http://www.rfc-editor.org/rfc/rfc2616.txt">RFC2616</a>
for more information about these); for example: <code>Host</code>,
- <code>User-Agent</code>, <code>Referer</code>, and
+ <code>User-Agent</code>, <code>Referer</code>, and
<code>Accept-Language</code>. A regular expression may be
used to specify a set of request headers.</li>
@@ -308,7 +308,7 @@ results.</li>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets environment variables based on attributes of the request
without respect to case</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>SetEnvIfNoCase <em>attribute regex
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>SetEnvIfNoCase <em>attribute regex
[!]env-variable</em>[=<em>value</em>]
[[!]<em>env-variable</em>[=<em>value</em>]] ...</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ja
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ja?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ja [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ja [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 658546:1132802 (outdated) -->
+<!-- English Revision: 658546:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ko
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ko?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ko [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.ko [euc-kr] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 151408:1132802 (outdated) -->
+<!-- English Revision: 151408:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.tr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.tr?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.tr [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml.tr [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.tr.xsl"?>
-<!-- English Revision: 658546:1132802 (outdated) -->
+<!-- English Revision: 658546:1174747 (outdated) -->
<!-- =====================================================
Translated by: Nilgün Belma Bugüner <nilgun belgeler.org>
Reviewed by: Orhan Berent <berent belgeler.org>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_so.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_so.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_so.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_so.html.en Sat Oct 1 20:57:36 2011
@@ -32,7 +32,7 @@ modules into the server at start-up or r
<tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>so_module</td></tr>
<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_so.c</td></tr>
-<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>This is a Base module (always included) on
+<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>This is a Base module (always included) on
Windows</td></tr></table>
<h3>Summary</h3>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ja
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ja?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ja [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ja [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 420990:932389 (outdated) -->
+<!-- English Revision: 420990:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ko
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ko?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ko [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_so.xml.ko [euc-kr] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 420990:932389 (outdated) -->
+<!-- English Revision: 420990:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_so.xml.tr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_so.xml.tr?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_so.xml.tr [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_so.xml.tr [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.tr.xsl"?>
-<!-- English Revision: 420990:932389 (outdated) -->
+<!-- English Revision: 420990:1174747 (outdated) -->
<!-- =====================================================
Translated by: Nilgün Belma Bugüner <nilgun belgeler.org>
Reviewed by: Orhan Berent <berent belgeler.org>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_speling.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_speling.html.en?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_speling.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_speling.html.en Sat Oct 1 20:57:36 2011
@@ -80,7 +80,7 @@ misspellings.</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_speling</td></tr>
</table>
- <p>When set, this directive limits the action of the spelling correction to lower/upper case changes.
+ <p>When set, this directive limits the action of the spelling correction to lower/upper case changes.
Other potential corrections are not performed.</p>
@@ -88,7 +88,7 @@ misspellings.</td></tr>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="CheckSpelling" id="CheckSpelling">CheckSpelling</a> <a name="checkspelling" id="checkspelling">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Enables the spelling
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Enables the spelling
module</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CheckSpelling on|off</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CheckSpelling Off</code></td></tr>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ja
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ja?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ja [utf-8] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ja [utf-8] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 420990:945103 (outdated) -->
+<!-- English Revision: 420990:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ko
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ko?rev=1178089&r1=1178088&r2=1178089&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ko [euc-kr] (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_speling.xml.ko [euc-kr] Sat Oct 1 20:57:36 2011
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 395228:945103 (outdated) -->
+<!-- English Revision: 395228:1174747 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more