fetch hangs when trying to http-download from http://ftp5.de.FreeBSD.org/

[Dominic Fandrey]

This is an example, I can download the file with firefox,
but fetch hangs infinitely, even though HTTP_TIMEOUT is set.
http://ftp5.de.FreeBSD.org/pub/FreeBSD/ports/amd64/packages-8-stable/All/ecore-txt-0.9.9.042.tbz

The HTTP headers with firefox:
GET /pub/FreeBSD/ports/amd64/packages-8-stable/All/ecore-txt-0.9.9.042.tbz HTTP/1.1
Host: ftp5.de.freebsd.org
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-GB; rv:1.9.2.12) Gecko/20101029 Firefox/3.6.12
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: UTF-8,*
Keep-Alive: 15
Connection: keep-alive
Cache-Control: no-cache

HTTP/1.1 200 OK
Date: Fri, 05 Nov 2010 18:06:36 GMT
Server: Cherokee/1.0.1 (UNIX)
Etag: 4c9492b8=19c2
Last-Modified: Sat, 18 Sep 2010 10:21:44 GMT
Content-Length: 6594


The output of fetch -vv:
scheme:   [http]
user:     []
password: []
host:     [ftp5.de.FreeBSD.org]
port:     [0]
document: [/pub/FreeBSD/ports/amd64/packages-8-stable/All/ecore-txt-0.9.9.042.tbz]
---> ftp5.de.FreeBSD.org:80
looking up ftp5.de.FreeBSD.org
connecting to ftp5.de.FreeBSD.org:80
requesting http://ftp5.de.FreeBSD.org/pub/FreeBSD/ports/amd64/packages-8-stable/All/ecore-txt-0.9.9.042.tbz
>>> GET /pub/FreeBSD/ports/amd64/packages-8-stable/All/ecore-txt-0.9.9.042.tbz HTTP/1.1
>>> Host: ftp5.de.FreeBSD.org
>>> User-Agent: fetch libfetch/2.0
>>> Connection: close
>>> 
<<< HTTP/1.1 200 OK
<<< Connection: close
<<< Date: Fri, 05 Nov 2010 18:13:04 GMT
<<< Server: Cherokee/1.0.1 (UNIX)
<<< ETag: 4c9492b8=19c2
<<< Last-Modified: Sat, 18 Sep 2010 10:21:44 GMT
<<< Content-Length: 6594
last modified: [2010-09-18 10:21:44]
<<< 
content length: [6594]
offset 0, length -1, size -1, clength 6594
remote size / mtime: 6594 / 1284805304
ecore-txt-0.9.9.042.tbz                         0% of 6594  B    0  Bps


The last line stays like this until I kill the process.
I don't see anything that worries me in the headers, no idea what
goes wrong.

Regards

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?