Ticket #18486 (closed: fixed)
Multiple Content-Length headers for downloads
| Reported by: | tseaver | Owned by: | ceverest |
|---|---|---|---|
| Keywords: | SOG | Cc: | |
| Private: | no |
Description
Sourceforge is setting multiple 'Content-Length' headers for downloaded tarballs, which breaks installing them via setuptools::
$ wget -S -O /dev/null http://wwwsearch.sourceforge.net/mechanize/src/mechanize-0.2.4.tar.gz --2011-03-23 10:21:02-- http://wwwsearch.sourceforge.net/mechanize/src/mechanize-0.2.4.tar.gz Resolving wwwsearch.sourceforge.net... 216.34.181.96 Connecting to wwwsearch.sourceforge.net|216.34.181.96|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Server: Apache/2.2.3 (CentOS) Last-Modified: Thu, 28 Oct 2010 20:57:05 GMT ETag: "5d707-493b395976a40" Content-Length: 382727 Expires: Fri, 25 Mar 2011 14:21:02 GMT Content-Type: application/x-gzip Content-Length: 382727 Date: Wed, 23 Mar 2011 14:21:02 GMT X-Varnish: 929535497 Age: 0 Via: 1.1 varnish Connection: keep-alive Length: 382727 (374K) [application/x-gzip] Saving to: `/dev/null' 100%[======================================>] 382,727 543K/s in 0.7s 2011-03-23 10:21:03 (543 KB/s) - `/dev/null' saved [382727/382727]
I have opened an issue with patch for setuptools[1] to work around the issue, but RFC 2616 doesn't contemplate sending more than one copy of the header.
Change History
Note: See
TracTickets for help on using
tickets.