Commit 924f74ce authored by Ben Laurie's avatar Ben Laurie
Browse files

Add documentation for nokeepalive and force-response-1.0. 


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77674 13f79535-47bb-0310-9956-ffa450edef68
parent 484e0d25

docs/manual/env.html

0 → 100644
+30 −0
Changes for docs/manual/env.html: 30 added lines, 0 removed lines.
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<HTML>

<HEAD>

<TITLE>Special Purpose Environment Variables</TITLE>

</HEAD>



<BODY>

<!--#include virtual="header.html" -->

<h1>Special Purpose Environment Variables</h1>

<P>Interoperability problems have led to the introduction of mechanisms to modify

the way Apache behaves when talking to particular clients. To make these

mechanisms as flexible as possible, they are invoked by defining environment

variables, typically with <A HREF=mod/mod_browser.html#browsermatch>BrowserMatch</A>, though <A HREF=mod/mod_env.html#setenv>SetEnv</A> and

<A HREF=mod/mod_env.html#passenv>PassEnv</A> could also be used, for example.</P>

<H2>nokeepalive</H2>

This disables <A HREF=mod/core.html#keepalive>KeepAlive</A> when set. Because

of problems with Netscape 2.x and KeepAlive, we recommend the following

directive be used:

<BLOCKQUOTE><CODE>

BrowserMatch Mozilla/2 nokeepalive

</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.



<!--#include virtual="footer.html" -->

</BODY>

</HTML>

docs/manual/env.html.en

0 → 100644
+30 −0
Changes for docs/manual/env.html.en: 30 added lines, 0 removed lines.
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<HTML>

<HEAD>

<TITLE>Special Purpose Environment Variables</TITLE>

</HEAD>



<BODY>

<!--#include virtual="header.html" -->

<h1>Special Purpose Environment Variables</h1>

<P>Interoperability problems have led to the introduction of mechanisms to modify

the way Apache behaves when talking to particular clients. To make these

mechanisms as flexible as possible, they are invoked by defining environment

variables, typically with <A HREF=mod/mod_browser.html#browsermatch>BrowserMatch</A>, though <A HREF=mod/mod_env.html#setenv>SetEnv</A> and

<A HREF=mod/mod_env.html#passenv>PassEnv</A> could also be used, for example.</P>

<H2>nokeepalive</H2>

This disables <A HREF=mod/core.html#keepalive>KeepAlive</A> when set. Because

of problems with Netscape 2.x and KeepAlive, we recommend the following

directive be used:

<BLOCKQUOTE><CODE>

BrowserMatch Mozilla/2 nokeepalive

</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.



<!--#include virtual="footer.html" -->

</BODY>

</HTML>