rather complex protocols to communicate synchronisation information
between the client-
Date: Mon, 22 Aug 2005 19:21:21 +0200
In-Reply-To: <[EMAIL PROTECTED]> (Tom Huckstep's message of "Fri, 24
Jun 2005 14:29:02 +0100")
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
> If I set the parent proxy and try to open a web page, I get the following
> response from the parent proxy:
>
> 400 Bad Request
> Error occurred:
>
> No Host header found in HTTP/1.1 request
Thanks for the report, this is indeed a non-conformance in Polipo. It
looks like HTTP/1.1 is even more bizarre than I thought.
>From RFC 2616, Section 5.2:
If Request-URI is an absoluteURI, the host is part of the
Request-URI. Any Host header field value in the request MUST be
ignored.
Polipo always uses absoluteURIs in the requests it send to an upstream
proxy. Which is why it never sends a Host header.
Section 14.23:
A client MUST include a Host header field in all HTTP/1.1 request
messages.
So it looks that although a Host header to a parent proxy is always
ignored, it is still compulsory to include one. Stupid HTTP.
I'll fix this ASAP.
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
