by Brian Hankin » Thu, 27 Sep 2001 08:11:15
My problem is this: When using mozilla, the http request is HTTP/1.1.
The request passed to the second (DMZ) proxy is HTTP/1.0.
How can I configure the first prxy to make a 1.1 request? Many web site
don't work when this situation occurs.
Thanks.
Brian
by Justin Erenkrant » Thu, 27 Sep 2001 11:05:03
> My problem is this: When using mozilla, the http request is HTTP/1.1.
> The request passed to the second (DMZ) proxy is HTTP/1.0.
> How can I configure the first prxy to make a 1.1 request? Many web site
> don't work when this situation occurs.
The proxy should be able to seamlessly make the transition from HTTP/1.0
to HTTP/1.1. What proxy are you using? It sounds like mod_proxy - you
may have better luck with Squid.
Most proxies do not use HTTP/1.1 because they do not support all of the
requirements set forth in RFC 2616.
Justin Erenkrantz
by Brian Hankin » Thu, 27 Sep 2001 11:39:59
>>I am using an apache proxy, which goes upstream to another apache proxy
>>in a DMZ.
>>My problem is this: When using mozilla, the http request is HTTP/1.1.
>>The request passed to the second (DMZ) proxy is HTTP/1.0.
>>How can I configure the first prxy to make a 1.1 request? Many web site
>>don't work when this situation occurs.
> Why wouldn't it work? Are you seeing a functional problem?
> The proxy should be able to seamlessly make the transition from HTTP/1.0
> to HTTP/1.1. What proxy are you using? It sounds like mod_proxy - you
> may have better luck with Squid.
> Most proxies do not use HTTP/1.1 because they do not support all of the
> requirements set forth in RFC 2616.
> Justin Erenkrantz
I am considering squid, but I'm not looking forward to getting the LDAP
authenticatoin working again.
Thanks for the input.
--Brian
by Brian Hankin » Sun, 30 Sep 2001 08:37:46
>>> I am using an apache proxy, which goes upstream to another apache proxy
>>> in a DMZ.
>>> My problem is this: When using mozilla, the http request is HTTP/1.1.
>>> The request passed to the second (DMZ) proxy is HTTP/1.0.
>>> How can I configure the first prxy to make a 1.1 request? Many web site
>>> don't work when this situation occurs.
>> Why wouldn't it work? Are you seeing a functional problem?
>> The proxy should be able to seamlessly make the transition from HTTP/1.0
>> to HTTP/1.1. What proxy are you using? It sounds like mod_proxy - you
>> may have better luck with Squid.
>> Most proxies do not use HTTP/1.1 because they do not support all of the
>> requirements set forth in RFC 2616.
>> Justin Erenkrantz
> You're correct, apache 1.3.20 with mod_proxy. I've encountered several
> web sites that have not successfully navigated the 1.1 -> 1.0 transition
> (I get a "document contains no data" error). Most notably
> www.hardocp.com and www.anandtech.com fail outright.
> I am considering squid, but I'm not looking forward to getting the LDAP
> authenticatoin working again.
> Thanks for the input.
> --Brian
--Brian
by Justin Erenkrant » Sun, 30 Sep 2001 16:50:24
Somehow that doesn't shock me.Quote:> Gave up on apache. Got squid working with LDAP, and this combination
> works much better.
mod_proxy has always been neglected until very recently in the 2.0 series.
I would expect that 2.0's mod_proxy is going to be usable, but 1.3's is
definitely not going to be usable except for very controlled
circumstances.
Justin Erenkrantz
1. apache http proxy - http/1.0 vs http/1.1
Hello,
I have setup an apache proxy, which seems to work fine. But, I found
out that it doesn't not answer back http/1.1 with a http/1.1 response.
The request comes in as 1.1, but the proxy answer back with 1.0. Is
there some special configuration I need to set in httpd.conf for it
to answer with a 1.1 response?
When I send traffic to the backend machine it will answer with a 1.1
response just fine. We are using the same version of apache for both
the proxy and actual backend server.
Any hints as to what I'm missing? Thanks.
-Dan
Sent via Deja.com http://www.deja.com/
Before you buy.
2. Strange NFS Client Behavior
3. HTTP/1.0 vs HTTP/1.1 question
6. how to change hostname in a Sun cluster 3.0
8. ldap_simple_bind_s() takes too much time!
9. Client ->(HTTPS) -> Proxy -> (HTTP) -> Server
10. HTTP/1.0" 304 0 HTTP/1.0 304 Not
11. apache proxy module support HTTP 1.1??
12. apache proxy server and http/1.1