Bug#36081: marked as done (apt-get http header parsing too strict)
Your message dated Wed, 14 Apr 1999 17:40:20 -0600 (MDT)
with message-id <[🔎] Pine.LNX.3.96.990414173453.23229B-100000@Wakko.deltatee.com>
and subject line Bug#36081: apt-get http header parsing too strict
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(administrator, Debian bugs database)
Received: (at submit) by bugs.debian.org; 14 Apr 1999 21:39:04 +0000
Received: (qmail 19203 invoked from network); 14 Apr 1999 21:39:04 -0000
Received: from solar.sky.net (HELO sky.net) (josh@209.90.0.4)
by master.debian.org with SMTP; 14 Apr 1999 21:39:04 -0000
Received: (from josh@localhost)
by sky.net (8.8.5/8.8.5) id QAA23704;
Wed, 14 Apr 1999 16:38:58 -0500 (CDT)
Message-Id: <[🔎] 199904142138.QAA23704@sky.net>
X-Mailer: exmh version 2.0.2 2/24/98 (debian)
To: submit@bugs.debian.org
Subject: apt-get http header parsing too strict
From: Josh Wilmes <josh@hitchhiker.org>
Reply-To: Josh Wilmes <josh@hitchhiker.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Apr 1999 17:38:56 -0400
Sender: josh@sky.net
Package: apt
Version: 0.1.9
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.
--Josh
--
Josh Wilmes (josh@hitchhiker.org) | http://www.hitchhiker.org
Reply to: