code for the request (see below) is 401, then this value
should not be trusted because the user is not yet
authenticated. If the document is not password protected,
- this entry will be "<code>-</code>" just like the previous
+ this part will be "<code>-</code>" just like the previous
one.</dd>
<dt><code>[10/Oct/2000:13:55:36 -0700]</code>
<dt><code>2326</code> (<code>%b</code>)</dt>
- <dd>The last entry indicates the size of the object returned
+ <dd>The last part indicates the size of the object returned
to the client, not including the response headers. If no
content was returned to the client, this value will be
"<code>-</code>". To log "<code>0</code>" for no content, use
<div id="quickview"><h3 class="directives">Directives</h3>
<p>This module provides no
directives.</p>
-<h3>See also</h3>
+<h3>Topics</h3>
+<ul id="topics">
+<li><img alt="" src="../images/down.gif" /> <a href="#env">Environment Variables</a></li>
+</ul><h3>See also</h3>
<ul class="seealso">
<li><code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code></li>
<li><code class="module"><a href="../mod/mod_proxy_connect.html">mod_proxy_connect</a></code></li>
</ul></div>
-
+<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>In addition to the configuration directives that control the
+ behaviour of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, there are a number of
+ <dfn>environment variables</dfn> that control the HTTP protocol
+ provider:</p>
+ <dl>
+ <dt>proxy-sendextracrlf</dt>
+ <dd>Causes proxy to send an extra CR-LF newline on the end of a
+ request. This is a workaround for a bug in some browsers.</dd>
+ <dt>force-proxy-request-1.0</dt>
+ <dd>Forces the proxy to send requests to the backend as HTTP/1.0
+ and disables HTTP/1.1 features.</dd>
+ <dt>proxy-nokeepalive</dt>
+ <dd>Forces the proxy to close the backend connection after
+ each request.</dd>
+ <dt>Proxy-Chain-Auth</dt>
+ <dd>If the proxy requires authentication, it will read and
+ consume the proxy authentication credentials sent by the client.
+ With <var>Proxy-Chain-Auth</var> it will <em>also</em> forward
+ the credentials to the next proxy in the chain. This may
+ be necessary if you have a chain of proxies that share
+ authentication information. <strong>Security Warning:</strong>
+ Do not set this unless you know you need it, as it forwards
+ sensitive information!</dd>
+ <dt>proxy-sendcl</dt>
+ <dd>HTTP/1.0 required all HTTP requests that include a body
+ (e.g. POST requests) to include a <var>Content-Length</var>
+ header. This environment variable forces the Apache proxy to
+ send this header to the backend server, regardless of what the
+ Client sent to the proxy. It ensures compatibility when
+ proxying for an HTTP/1.0 or unknown backend. However, it
+ may require the entire request to be buffered by the proxy,
+ so it becomes very inefficient for large requests.</dd>
+ <dt>proxy-sendchunks or proxy-sendchunked</dt>
+ <dd>This is the opposite of <var>proxy-sendcl</var>. It allows
+ 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>
+ </dl>
+</div>
</div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../en/mod/mod_proxy_http.html" title="English"> en </a></p>
projects / thirdparty / apache / httpd.git / commitdiff
