I think this came up a month ago and if I remember correctly the answer is:
The proxy is actually http/1.1 even though it reports itself as http/1.0.
This is a bug and is yet unfixed in the CVS tree.
I wasn't planning on fixing it myself because it's clearly in the realm of
the larger conversion-to-1.1 project. I'm surprised that this hasent been
an issue. Are keep-alives intended to be supported in the back end?
Because, this will clearly hinder keep-alives and maybe a few other
standard http/1.1 features.
Who is the main man on the http/1.1 upgrade?
|--------+-------------------------->
| | "Gael Seroul" |
| | <[EMAIL PROTECTED]|
| | ubill.com> |
| | |
| | 03/01/2002 03:12|
| | AM |
| | Please respond |
| | to modproxy-dev |
| | |
|--------+-------------------------->
>-----------------------------------------------------------------------------------------------------------------------|
|
|
| To: "Liste proxy apache" <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: mod_proxy and HTTP/1.1 request
|
>-----------------------------------------------------------------------------------------------------------------------|
Hi,
I'm using apache 1.3.23 with mod_proxy (now support HTTP/1.1). I used a
sniffer to trace all trafic beetween my browser, the proxy and the web
server.
The problem is that beetween browser and proxy the communication is done in
HTTP/1.1, but the proxy request on the web server is done in HTTP/1.0.
Is it a normal behaviour ?
Here the connection traces :
browser -> proxy
GET http://www.yahoo.com HTTP/1.1
Host: www.yahoo.com
Proxy-Connection: Keep-Alive
proxy -> web server
GET / HTTP/1.0
Host: www.yahoo.com
Connection: close
web server -> proxy
HTTP/1.0 200 OK
Connection: close
proxy -> browser
HTTP/1.1 200 OK
Transfert-Encoding: chunked
