Re: bin/45116: /usr/bin/ftp fails to parse Content-Range header

[Luke Mewburn <lukem%NetBSD.org@localhost>]

The following reply was made to PR bin/45116; it has been noted by GNATS.

From: Luke Mewburn <lukem%NetBSD.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/45116: /usr/bin/ftp fails to parse Content-Range header
Date: Sun, 17 Jul 2011 19:40:01 +1000

 --HjGz34yYE1BNnn/x
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Mon, Jul 04, 2011 at 12:00:00PM +0000, mspo%netbsd.org@localhost wrote:
   | >Number:         45116
   | >Category:       bin
   | >Synopsis:       /usr/bin/ftp fails to parse Content-Range header
   | I believe the parsing of Content-Range headers is broken in ftp.  This =
 is affecting a few packages in pkgsrc.
   | >How-To-Repeat:
   | ucspi-tcp $ ftp -d http://www.fefe.de/ucspi/ucspi-tcp-0.88-ipv6.diff19.=
 bz2
   |=20
   | isipv6addr: got 0 for http://www.fefe.de/ucspi/ucspi-tcp-0.88-ipv6.diff=
 19.bz2
   | fetch_url: `http://www.fefe.de/ucspi/ucspi-tcp-0.88-ipv6.diff19.bz2' pr=
 oxyenv `<null>'
   | parse_url: URL `http://www.fefe.de/ucspi/ucspi-tcp-0.88-ipv6.diff19.bz2'
   | parse_url: user `<null>' pass `<null>' host www.fefe.de port http(80) p=
 ath `/ucspi/ucspi-tcp-0.88-ipv6.diff19.bz2'
   | fetch_url: savefile `ucspi-tcp-0.88-ipv6.diff19.bz2'
   | Requesting http://www.fefe.de/ucspi/ucspi-tcp-0.88-ipv6.diff19.bz2
   | fetch_url: received `HTTP/1.1 200 Coming Up'
   | fetch_url: received `Accept-Ranges: bytes'
   | fetch_url: received `Server: Gatling/0.12'
   | fetch_url: received `Content-Type: application/octet-stream'
   | fetch_url: received `Content-Length: 22632'
   | fetch_url: parsed len as: 22632
   | fetch_url: received `Date: Mon, 04 Jul 2011 11:45:12 GMT'
   | fetch_url: received `Last-Modified: Thu, 19 Mar 2009 11:46:48 GMT'
   | parsed date as: Thu, 19 Mar 2009 07:46:48 -0400
   | fetch_url: received `Content-Range: bytes 0-22631/22632'
   | parsed range as: 0-22631/22632
   | ftp: Received unexpected Content-Range header
 
 I'm researching this issue.
 
 It looks like the http server (Gatling/0.12) is incorrectly sending
 a Content-Range response that wasn't requested (ftp didn't send a
 Range header in the request since you didn't use -R).
 
 It's also possible that the server has another bug in that it
 sends Content-Range in a reponse that isn't 206.
 
 I'm getting clarification from a member of the HTTP working group.
 
 --HjGz34yYE1BNnn/x
 Content-Type: application/pgp-signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.11 (NetBSD)
 
 iEYEARECAAYFAk4irfAACgkQpBhtmn8zJHK4CQCgl34+OJvdUqc4/qYbtpZyaQVd
 G+UAn3VPg8Fjo1NXLj56eWWd96DmamjA
 =lbUu
 -----END PGP SIGNATURE-----
 
 --HjGz34yYE1BNnn/x--