Re: [PATCH] Be more lenient with ap_proxy_read_headers in 2.0

2002-09-25 Thread Graham Leggett
Peter Van Biesen wrote: I've sent a patch doing the same some time ago, but it was not accepted so don't get your hopes up ;-). The big problem is that the code is starting to be so lenient it is getting silly. If a bogus header comes along (ie a header without a : in it) it is relatively

Re: [PATCH] Be more lenient with ap_proxy_read_headers in 2.0

2002-09-25 Thread Jim Jagielski
At 6:16 PM +0200 9/25/02, Graham Leggett wrote: The above two cases of brokenness are mutually exclusive. If a non-header is encountered when a header is expected, we have the choice of either assuming it's a header and ignoring it, or assuming the headers are over and starting the body. We

Re: [PATCH] Be more lenient with ap_proxy_read_headers in 2.0

2002-09-24 Thread Peter Van Biesen
I've sent a patch doing the same some time ago, but it was not accepted so don't get your hopes up ;-). Peter. Jim Jagielski wrote: In the 2.0 proxy, a bogus header line causes an immediate 502 error, whereas in 1.3, we try to handle it. The below patch attemps to make 2.0 a bit more