b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<?xml version="1.0"?>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<?xml-stylesheet type="text/xsl" href="/style/manual.en.xsl"?>

d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd

d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd

7db9f691a00ead175b03335457ca296a33ddf31bnd<modulesynopsis metafile="mod_proxy_http.xml.meta">

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<name>mod_proxy_http</name>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<description>HTTP support module for

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<module>mod_proxy</module></description>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<status>Extension</status>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<sourcefile>proxy_http.c</sourcefile>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<identifier>proxy_http_module</identifier>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<summary>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd <p>This module <em>requires</em> the service of <module

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd >mod_proxy</module>. It provides the features used for

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd proxying HTTP requests. <module>mod_proxy_http</module>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd supports HTTP/0.9, HTTP/1.0 and HTTP/1.1. It does <em>not</em>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd provide any caching abilities. If you want to set up a caching

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd proxy, you might want to use the additional service of the

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd <module>mod_cache</module> module.</p>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd <p>Thus, in order to get the ability of handling HTTP proxy requests,

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd <module>mod_proxy</module> and <module>mod_proxy_http</module>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd have to be present in the server.</p>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd <note type="warning"><title>Warning</title>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd <p>Do not enable proxying until you have <a

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd href="mod_proxy.html#access">secured your server</a>. Open proxy

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd servers are dangerous both to your network and to the Internet at

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd large.</p>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd </note>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd</summary>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<seealso><module>mod_proxy</module></seealso>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd<seealso><module>mod_proxy_connect</module></seealso>

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq<section id="env"><title>Environment Variables</title>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <p>In addition to the configuration directives that control the

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq behaviour of <module>mod_proxy</module>, there are a number of

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dfn>environment variables</dfn> that control the HTTP protocol

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq provider:</p>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dl>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dt>proxy-sendextracrlf</dt>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dd>Causes proxy to send an extra CR-LF newline on the end of a

a0dd9c437e3d11e11de853185e12b03028a2b980niq request. This is a workaround for a bug in some browsers.</dd>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dt>force-proxy-request-1.0</dt>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dd>Forces the proxy to send requests to the backend as HTTP/1.0

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq and disables HTTP/1.1 features.</dd>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dt>proxy-nokeepalive</dt>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dd>Forces the proxy to close the backend connection after

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq each request.</dd>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dt>Proxy-Chain-Auth</dt>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dd>If the proxy requires authentication, it will read and

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq consume the proxy authentication credentials sent by the client.

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq With <var>Proxy-Chain-Auth</var> it will <em>also</em> forward

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq the credentials to the next proxy in the chain. This may

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq be necessary if you have a chain of proxies that share

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq authentication information. <strong>Security Warning:</strong>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq Do not set this unless you know you need it, as it forwards

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq sensitive information!</dd>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dt>proxy-sendcl</dt>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dd>HTTP/1.0 required all HTTP requests that include a body

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq (e.g. POST requests) to include a <var>Content-Length</var>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq header. This environment variable forces the Apache proxy to

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq send this header to the backend server, regardless of what the

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq Client sent to the proxy. It ensures compatibility when

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq proxying for an HTTP/1.0 or unknown backend. However, it

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq may require the entire request to be buffered by the proxy,

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq so it becomes very inefficient for large requests.</dd>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dt>proxy-sendchunks or proxy-sendchunked</dt>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq <dd>This is the opposite of <var>proxy-sendcl</var>. It allows

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq request bodies to be sent to the backend using chunked transfer

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq encoding. This allows the request to be efficiently streamed,

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq but requires that the backend server supports HTTP/1.1.</dd>

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq <dt>proxy-interim-response</dt>

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq <dd>This variable takes values <code>RFC</code> or

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq <code>Suppress</code>. Earlier httpd versions would suppress

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq HTTP interim (1xx) responses sent from the backend. This is

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq technically a violation of the HTTP protocol. In practice,

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq if a backend sends an interim response, it may itself be

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq extending the protocol in a manner we know nothing about,

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq or just broken. So this is now configurable: set

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq <code>proxy-interim-response RFC</code> to be fully protocol

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq compliant, or <code>proxy-interim-response Suppress</code>

c6f2d0c33368d0ff719e176c3bef9c2ea5177d43niq to suppress interim responses.</dd>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq </dl>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq</section>

3d5bba702bba34c9c15e4b2e3bc685e4249e51a5niq

b73a2be324e0b7fda7671ffc1e580a83a2af0d61nd</modulesynopsis>