what went wrong and how to fix it.</p>
<p>The error log is usually written to a file (typically
- <code>error_log</code> on unix systems and
- <code>error.log</code> on Windows and OS/2). On unix systems it
+ <code>error_log</code> on Unix systems and
+ <code>error.log</code> on Windows and OS/2). On Unix systems it
is also possible to have the server send errors to
<code>syslog</code> or <a href="#piped">pipe them to a
program</a>.</p>
</code></p></div>
<p>The first item in the log entry is the date and time of the
- message. The second entry lists the severity of the error being
+ message. The second item lists the severity of the error being
reported. The <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code>
directive is used to control the types of errors that are sent
to the error log by restricting the severity level. The third
- entry gives the IP address of the client that generated the
+ item gives the IP address of the client that generated the
error. Beyond that is the message itself, which in this case
indicates that the server has been configured to deny the
client access. The server reports the file-system path (as
file.</p>
<p>During testing, it is often useful to continuously monitor
- the error log for any problems. On unix systems, you can
+ the error log for any problems. On Unix systems, you can
accomplish this using:</p>
<div class="example"><p><code>
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.de.xsl"?>
-<!-- English Revision: 167959:580502 (outdated) -->
+<!-- English Revision: 167959:583289 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?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: 190982:580502 (outdated) -->
+<!-- English Revision: 190982:583289 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
critical because clients can only contact the hosts that you
have specifically configured.</p>
+ <p><strong>See Also</strong> the <a href="mod_proxy_http.html#env">Proxy-Chain-Auth</a> environment variable.</p>
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="startup" id="startup">Slow Startup</a></h2>
<?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: 189754:581253 (outdated) -->
+<!-- English Revision: 189754:582476 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<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 servers.</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>
+ <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>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../en/mod/mod_proxy_http.html" title="English"> en </a></p>
<dd><p><code class="module"><a href="./mod/mod_dbd.html">mod_dbd</a></code>, together with the apr_dbd framework,
brings direct SQL support to modules that need it. Supports
connection pooling in threaded MPMs.</p>
- <p><strong>Windows Users</strong> please note that this is not
- yet included in the standard windows build. If you try to use
- it on the Windows platform, please let us know how you get on.</p>
</dd>
</dl>
<?xml version='1.0' encoding='EUC-KR' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.ko.xsl"?>
-<!-- English Revision: 105989:574882 (outdated) -->
+<!-- English Revision: 105989:583232 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.pt-br.xsl"?>
-<!-- English Revision: 151408:574882 (outdated) -->
+<!-- English Revision: 151408:583232 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
projects / apache / commitdiff