Re: Serious bug: fou4s v0.11.3 doesn't work on Suse < 9
Lars Ellenberg <[email protected]> Thu, 15 Apr 2004 19:10:55 +0200
| Newsgroups | gmane.linux.suse.fou4s.devel |
|---|---|
| Message-ID | <X1zmIpBktph/[email protected]> |
> Care to check yourself with ftp.leo.org? I use this line:
> Server=http://ftp.leo.org/pub/comp/os/unix/linux/suse/suse
transscript:
>> w3m -dump_head http://ftp.gwdg.de/...
>HEAD /pub/linux/suse/ftp.suse.com/suse/i386/update/8.1/patches/3ddiag-51213 HTTP/1.0
>User-Agent: w3m/0.4.1-m17n-20030308
>Accept: text/*, image/*, application/*, video/*, audio/*
>Accept-Encoding: gzip, compress, bzip, bzip2, deflate
>Accept-Language: en;q=1.0
>Host: ftp.gwdg.de
--
<HTTP/1.1 200 OK
<Date: Thu, 15 Apr 2004 16:50:07 GMT
<Server: Apache/1.3.27 (Linux/SuSE) PHP/4.3.1 mod_perl/1.27
<Last-Modified: Tue, 20 Jan 2004 18:31:16 GMT
<ETag: "4c41a9-6b4-400d73f4"
<Accept-Ranges: bytes
<Content-Length: 1716
<Connection: close
<Content-Type: text/plain
>> w3m -dump_head http://ftp.leo.org/...
>HEAD /pub/comp/os/unix/linux/suse/suse/i386/update/8.1/patches/3ddiag-51213 HTTP/1.0
>User-Agent: w3m/0.4.1-m17n-20030308
>Accept: text/*, image/*, application/*, video/*, audio/*
>Accept-Encoding: gzip, compress, bzip, bzip2, deflate
>Accept-Language: en;q=1.0
>Host: ftp.leo.org
--
<HTTP/1.1 200 OK
<Date: Thu, 15 Apr 2004 16:50:11 GMT
<Server: Apache/2.0.49 (Unix)
<Last-Modified: Tue, 20 Jan 2004 18:31:16 GMT
<ETag: "73859d-6b4-468de500"
<Accept-Ranges: bytes
<Content-Length: 1716
<Connection: close
<Content-Type: text/plain; charset=ISO-8859-1
looks good so far.
>> now, wget -N -c http://ftp.gwdg.de/...
>HEAD /pub/linux/suse/ftp.suse.com/suse/i386/update/8.1/patches/3ddiag-51213 HTTP/1.0
>User-Agent: Wget/1.8.2
>Host: ftp.gwdg.de
>Accept: */*
>Connection: Keep-Alive
>Range: bytes=1716-
--
<HTTP/1.1 416 Requested Range Not Satisfiable
<Date: Thu, 15 Apr 2004 16:50:18 GMT
<Server: Apache/1.3.27 (Linux/SuSE) PHP/4.3.1 mod_perl/1.27
<Last-Modified: Tue, 20 Jan 2004 18:31:16 GMT
<ETag: "4c41a9-6b4-400d73f4"
<Accept-Ranges: bytes
<Content-Length: 0
<Content-Range: bytes */1716
<Keep-Alive: timeout=15, max=100
<Connection: Keep-Alive
<Content-Type: text/plain
Resolving ftp.gwdg.de... done.
Connecting to ftp.gwdg.de[134.76.11.100]:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
exit code 0
>> and finally, wget -N -c http://ftp.leo.org/...
>HEAD /pub/comp/os/unix/linux/suse/suse/i386/update/8.1/patches/3ddiag-51213 HTTP/1.0
>User-Agent: Wget/1.8.2
>Host: ftp.leo.org
>Accept: */*
>Connection: Keep-Alive
>Range: bytes=1716-
--
<HTTP/1.1 416 Requested Range Not Satisfiable
<Date: Thu, 15 Apr 2004 16:50:27 GMT
<Server: Apache/2.0.49 (Unix)
<Keep-Alive: timeout=15, max=100
<Connection: Keep-Alive
<Content-Type: text/html; charset=iso-8859-1
Resolving ftp.leo.org... done.
Connecting to ftp.leo.org[131.159.72.23]:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
Continued download failed on this file, which conflicts with `-c'.
Refusing to truncate existing file `3ddiag-51213'.
exit code: 1
So, the issue seem to be that leo (apache 2.0.49) does NOT include the
<Accept-Ranges: bytes
<Content-Length: 0
<Content-Range: bytes */1716
information, which gwdg (apache 1.3.27) DOES provide.
Maybe someone familiar with apache vs. apache can give a hint whether
this is a apache config problem, a problem with the apache versions,
a problem with the leo reply being out of spec (non-rfc-conform[tm]) or
a problem with wget (mis)interpreting the server response.
also interesting that both apaches answer a HTTP/1.0 request with a
HTTP/1.1 reply, but this may be legal :)
Cheers,
Lars Ellenberg
--