httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Jenkins <>
Subject [users@httpd] Incorrect response to range request past end of file
Date Fri, 22 Jan 2010 16:40:51 GMT

I noticed that "wget -c" chokes on already completed downloads.  It 
retries indefinitely - because it doesn't like the response Apache sends.

RFC 2616 suggests apache SHOULD return "416 Requested Range Not 
Satisfiable" in this case.  Instead, Apache returns "206 Partial 
content" with  a Content-Length of 0.  That's arguably legal -- but then 
it says "Content-Range: bytes */9597", which is not legal for a 206 
response.  "bytes *" means "invalid range", and is only allowed for a 416.

Is this a known bug, or should I report it to Bugzilla?


References: <>

Steps to reproduce:

1. Download a page e.g."wget"

 -> index.html is successfully downloaded

2. Try re-downloading it with e.g. "wget -S -c"

 -> wget fails, retrying indefinitely:

--2010-01-22 15:56:17--
Resolving localhost..., ::1
Connecting to localhost||:8123... connected.
Proxy request sent, awaiting response...
HTTP/1.1 206 Partial content
Content-Length: 0
Content-Range: bytes */9597
ETag: "d12b7b-257d-47d6a579d5dbc"
Date: Fri, 22 Jan 2010 15:56:15 GMT
Last-Modified: Mon, 18 Jan 2010 06:19:56 GMT
Server: Apache/2.3.5 (Unix) mod_ssl/2.3.5 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Age: 1
Connection: close

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message