You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by no...@apache.org on 2007/12/15 19:08:13 UTC
svn commit: r604471 - in /httpd/httpd/branches/2.2.x/docs/manual/mod:
mod_proxy_balancer.html.en mod_proxy_balancer.xml.ja mod_proxy_http.html.en
mod_rewrite.html.en mod_status.html.en
Author: noodl
Date: Sat Dec 15 10:08:11 2007
New Revision: 604471
URL: http://svn.apache.org/viewvc?rev=604471&view=rev
Log:
Update transformations
Modified:
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.html.en
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.xml.ja
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_http.html.en
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_rewrite.html.en
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_status.html.en
Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.html.en?rev=604471&r1=604470&r2=604471&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.html.en Sat Dec 15 10:08:11 2007
@@ -66,7 +66,7 @@
<p>At present, there are 2 load balancer scheduler algorithms available
for use: Request Counting and Weighted Traffic 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#proxy">Proxy</a></code> directive for
+ the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> directive for
more information.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.xml.ja
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.xml.ja?rev=604471&r1=604470&r2=604471&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.xml.ja [iso-2022-jp] (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_balancer.xml.ja [iso-2022-jp] Sat Dec 15 10:08:11 2007
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="iso-2022-jp"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 153116:472114 (outdated) -->
+<!-- English Revision: 153116:604470 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_http.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_http.html.en?rev=604471&r1=604470&r2=604471&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_http.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_http.html.en Sat Dec 15 10:08:11 2007
@@ -98,6 +98,17 @@
request bodies to be sent to the backend using chunked transfer
encoding. This allows the request to be efficiently streamed,
but requires that the backend server supports HTTP/1.1.</dd>
+ <dt>proxy-interim-response</dt>
+ <dd>This variable takes values <code>RFC</code> or
+ <code>Suppress</code>. Earlier httpd versions would suppress
+ HTTP interim (1xx) responses sent from the backend. This is
+ technically a violation of the HTTP protocol. In practice,
+ if a backend sends an interim response, it may itself be
+ extending the protocol in a manner we know nothing about,
+ or just broken. So this is now configurable: set
+ <code>proxy-interim-response RFC</code> to be fully protocol
+ compliant, or <code>proxy-interim-response Suppress</code>
+ to suppress interim responses.</dd>
</dl>
</div>
</div>
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=604471&r1=604470&r2=604471&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 Sat Dec 15 10:08:11 2007
@@ -436,7 +436,15 @@
value of a header sent in the HTTP request.
Example: <code>%{HTTP:Proxy-Connection}</code> is
the value of the HTTP header
- ``<code>Proxy-Connection:</code>''.</li>
+ ``<code>Proxy-Connection:</code>''.
+ <p>If a HTTP header is used in a condition this header is added to
+ the Vary header of the response in case the condition evaluates to
+ to true for the request. It is <strong>not</strong> added if the
+ condition evaluates to false for the request. Adding the HTTP header
+ to the Vary header of the response is needed for proper caching.</p>
+ <p>It has to be kept in mind that conditions follow a short circuit
+ logic in the case of the '<strong><code>ornext|OR</code></strong>' flag
+ so that certain conditions might not be evaluated at all.</p></li>
<li>
<code>%{LA-U:variable}</code> can be used for look-aheads which perform
@@ -594,6 +602,16 @@
Without this flag you would have to write the condition/rule
pair three times.
</li>
+
+ <li>'<strong><code>novary|NV</code></strong>'
+ (<strong>n</strong>o <strong>v</strong>ary)<br />
+ If a HTTP header is used in the condition, this flag prevents
+ this header from being added to the Vary header of the response. <br />
+ Using this flag might break proper caching of the response if
+ the representation of this response varies on the value of this header.
+ So this flag should be only used if the meaning of the Vary header
+ is well understood.
+ </li>
</ul>
</li>
</ol>
@@ -1123,7 +1141,7 @@
<dd>A <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-relative path to the
resource to be served. Note that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
tries to guess whether you have specified a file-system path
- or a URL-path by checking to see if the first segement of the
+ or a URL-path by checking to see if the first segment of the
path exists at the root of the file-system. For example, if
you specify a <em>Substitution</em> string of
<code>/www/file.html</code>, then this will be treated as a
Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_status.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_status.html.en?rev=604471&r1=604470&r2=604471&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_status.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_status.html.en Sat Dec 15 10:08:11 2007
@@ -72,6 +72,7 @@
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
<li><img alt="" src="../images/down.gif" /> <a href="#extendedstatus">ExtendedStatus</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#seerequesttail">SeeRequestTail</a></li>
</ul>
<h3>Topics</h3>
<ul id="topics">
@@ -149,6 +150,29 @@
enabled or disabled on a virtualhost-by-virtualhost basis.
The collection of extended status information can slow down
the server.</p>
+
+</div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="directive-section"><h2><a name="SeeRequestTail" id="SeeRequestTail">SeeRequestTail</a> <a name="seerequesttail" id="seerequesttail">Directive</a></h2>
+<table class="directive">
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Determine if mod_status displays the first 63 characters
+of a request or the last 63, assuming the request itself is greater than
+63 chars.</td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>SeeRequestTail On|Off</code></td></tr>
+<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>SeeRequestTail Off</code></td></tr>
+<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr>
+<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_status</td></tr>
+<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>SeeRequestTail is only available in Apache 2.2.7 and
+later.</td></tr>
+</table>
+ <p>mod_status with ExtendedStatus On displays the actual request being
+ handled. For historical purposes, only 63 characters of the request
+ are actually stored for display purposes. This directive
+ controls whether the 1st 63 characters are stored (the previous
+ behavior and the default) or if the last 63 characters are. This
+ is only applicable, of course, if the length of the request is
+ 64 characters or greater.</p>
</div>
</div>