patch against the xml is attached, some comments would be appreciated :)

TIA, nd
-- 
Real programmers confuse Christmas and Halloween because
DEC 25 = OCT 31.  -- Unknown

                                      (found in ssl_engine_mutex.c)

Index: manual/mod/mod_proxy.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_proxy.xml,v
retrieving revision 1.16
diff -u -r1.16 mod_proxy.xml
--- manual/mod/mod_proxy.xml    1 Mar 2003 01:28:46 -0000       1.16
+++ manual/mod/mod_proxy.xml    3 Apr 2003 19:54:51 -0000
@@ -310,6 +310,34 @@
 </usage>
 </directivesynopsis>
 
+<directivesynopsis>
+<name>ProxyBadHeader</name>
+<description>Determines how to handle bad header lines in a
+response</description>
+<syntax>ProxyBadHeader IsError|Ignore|StartBody</syntax>
+<default>ProxyBadHeader IsError</default>
+<contextlist><context>server config</context><context>virtual host</context>
+</contextlist>
+
+<usage>
+<p>The <directive>ProxyBadHeader</directive> directive determines the behaviour
+of <module>mod_proxy</module> if it receives syntactically invalid header lines
+(i.e. containing no colon). The following arguments are possible:</p>
+<dl>
+<dt><code>IsError</code></dt>
+<dd>Abort the request and end up with a 502 (Bad Gateway) response. This is the
+default behaviour.</dd>
+
+<dt><code>Ignore</code></dt>
+<dd>Treat bad header lines entirely as if they weren't sent.</dd>
+
+<dt><code>StartBody</code></dt>
+<dd>When receiving the first bad header line, finish reading the headers and
+treat the remainder as body. This helps to work around buggy backend servers
+which forget to insert an empty line between the headers and the body.</dd>
+</dl>
+</usage>
+</directivesynopsis>
 
 <directivesynopsis type="section">
 <name>ProxyMatch</name>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to