Exactly! What do you think the remote origin server will do when it gets
the HTTP/1.0 header?
|--------+-------------------------->
| | "Gael Seroul" |
| | <[EMAIL PROTECTED]|
| | ubill.com> |
| | |
| | 03/07/2002 09:17|
| | AM |
| | Please respond |
| | to modproxy-dev |
| | |
|--------+-------------------------->
>-----------------------------------------------------------------------------------------------------------------------|
|
|
| To: <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: RE : mod_proxy and HTTP/1.1 request
|
>-----------------------------------------------------------------------------------------------------------------------|
I don't think the problem is just a version string error. The traffic I
saw beetween apache proxy and web server was in HTTP/1.0 (The header
was containing the Content-Length, no chunk appeared...)
The communication beetween apache proxy and web server is really in
HTTP/1.0.
Gael
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Envoy� : jeudi 7 mars 2002 17:23
> � : [EMAIL PROTECTED]
> Objet : Re: mod_proxy and HTTP/1.1 request
>
>
>
> The only place that I saw is where the proxy actually sends
> out the http version header. Just search for the string
> "HTTP/1.0" and change it to "HTTP/1.1" Once again, I'm
> surprised that nobody noticed this before. It seams like a
> huge change. I'm sure it will alter the way the proxy acts in
> some places (does the proxy support keep-alives on outgoing
> connections?)
