Re: Bug#36081: apt-get http header parsing too strict
On Wed, 14 Apr 1999, Josh Wilmes wrote:
> In methods/http/http.cc, apt-get's http method reports "http: Bad header line"
> if there is no space in any given header.
>
> This is not compliant with the HTTP standard, as I understand it. Spaces are
> conventionally used, but are not required. I am looking at
> http://www.w3c.org/Protocols/HTTP/1.1/draft-ietf-http-v11-spec-rev-06.txt,
> section 4.2.
>
> The HTTP cache that I am behind is appending "Connection:close" (with no
> space!) to the headers. I will report this bug to the vendor as well.
>
> For now, I just hacked it to ignore errors in the headers for my own machine.
> I don't have time to write a more well-thought out patch at this time, but I
> hope someone can deal with this.
This has been recently fixed in the CVS version of APT, I forget if it
made the cut for the latest potato release but it is available at
http://www.debian.org/~jgg/apt-ftp.deb
While you are talking to your vendor demand working HTTP/1.1 keep-alive
and pipelining support from them, maybe if enough people pressure them
they will.
Also, I'm not entirely sure, but I think these particular 'transparent'
proxies butcher Range: headers too, you might have trouble with http
resume.
Jason
Reply to: