Gael Seroul wrote: > I tried lots of combinations (with or without proxy, in HTTP 1.1 or > 1.0). > The communication beetween client and proxy is HTTP/1.1 (with > Proxy-Connection: Keep-Alive). > The communication beetween proxy and web server is HTTP/1.0 (with > Connection: Close). > It seems to be in line with RFC2616.
Connection: close is HTTP/1.1 protocol, not HTTP/1.0. Keepalives are not
supported in the v1.3 patch (they are in the 2.0 proxy) and are
negotiated "no" in the standard 1.1 way.
> It is just a shame that your original patch worked on both side in
> HTTP/1.1 and some code have got lost somewhere. Maybe it could cause
> problems under certain cases ?
What code were you testing? The current head of CVS (what will become
v1.3.24) has all the fixes in it, including the HTTP/1.1 to the backend.
The v1.3.23 code has got a whole bunch of bugs in it.
I am going to have to check this thoroughly - I have absolutely no idea
how it got changed back, as all traces of HTTP/1.0 behaviour was removed
when I wrote the patch. I'm a bit swamped with work right now, so I
cannot look at it in the next few days, but hopefully I will get to it
by next week.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
