in reply to I think Liz is right
in thread LWP::UserAgent Wrongly Uses HTTP/1.1

I tried doing the same, and Apache does return an HTTP/1.1 response. However, when I do the manual request, the webserver log shows the request was HTTP/1.0 — whereas the LWP::UserAgent method gets logged as an HTTP/1.1 request.
The challenge therefore appears to be getting the LWP::UserAgent script to emit a request that gets logged as HTTP/1.0.


davis
It's not easy to juggle a pregnant wife and a troubled child, but somehow I managed to fit in eight hours of TV a day.

Replies are listed 'Best First'.
Re: Re: I think Liz is right
by ysth (Canon) on Nov 28, 2003 at 11:54 UTC
    Don't know if this is helpful, but RFC 2616 saith:
    Due to interoperability problems with HTTP/1.0 proxies discovered since the publication of RFC 2068, caching proxies MUST, gateways MAY, and tunnels MUST NOT upgrade the request to the highest version they support. The proxy/gateway's response to that request MUST be in the same major version as the request.
    Also, RFC 2145 clarifies that the minor version the client sends has no relation to the version the server returns. Each should normally send the highest version for which it is at least conditionally compliant.
[reply]

In Section Seekers of Perl Wisdom