env.html revision c9b30964ca05a019026fa1d1b4c535b296b8ec9a
0N/A<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
0N/A<HTML>
0N/A<HEAD>
0N/A<TITLE>Special Purpose Environment Variables</TITLE>
0N/A</HEAD>
0N/A
0N/A<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
0N/A<BODY
0N/A BGCOLOR="#FFFFFF"
0N/A TEXT="#000000"
0N/A LINK="#0000FF"
0N/A VLINK="#000080"
0N/A ALINK="#FF0000"
0N/A>
0N/A<!--#include virtual="header.html" -->
0N/A<h1 ALIGN="CENTER">Special Purpose Environment Variables</h1>
0N/A<P>Interoperability problems have led to the introduction of
0N/Amechanisms to modify the way Apache behaves when talking to particular
0N/Aclients. To make these mechanisms as flexible as possible, they
0N/Aare invoked by defining environment variables, typically with
0N/A<A HREF="mod/mod_browser.html#browsermatch">BrowserMatch</A>, though
0N/A<A HREF="mod/mod_env.html#setenv">SetEnv</A> and
0N/A<A HREF="mod/mod_env.html#passenv">PassEnv</A> could also be used, for
0N/Aexample.</P>
0N/A
0N/A<H2>nokeepalive</H2>
0N/AThis disables <A HREF="mod/core.html#keepalive">KeepAlive</A> when set. Because
0N/Aof problems with Netscape 2.x and KeepAlive, we recommend the following
0N/Adirective be used:
0N/A<BLOCKQUOTE><CODE>
0N/ABrowserMatch Mozilla/2 nokeepalive
0N/A</CODE></BLOCKQUOTE>
<H2>force-response-1.0</H2>
This forces an HTTP/1.0 response when set. It was originally implemented as a
result of a problem with AOL's proxies. Some clients may not behave correctly
when given an HTTP/1.1 response, and this can be used to interoperate with
them.
<H2>downgrade-1.0</H2>
<p>This forces the request to be treated as a HTTP/1.0 request even if it
was in a later dialect.
<!--#include virtual="footer.html" -->
</BODY>
</HTML>