Re: SUMMARY fou4s update checking problems

/ 2004-12-08 12:20:16 +0000
\ David Corking:
> (Just joined the mailing list)
> 
> I am getting the same wget error (below) with my i586 8.2 Professional
> systems.
> 
> (1) Let me know any more info I can provide to help Markus or Lars
>     reproduce the problem.  Do you want me to attach output from 
>      bash -vx fou4s --ri <your options> &>fou.log
> 
> (2) Please confirm whether the error is (a) annoying noise or 
>     (b) preventing fou4s from completing.
> 
> The error occurs on second and subsequent time of executing fou4s (or
> 'wget -c')
> 
> Best regards, David Corking
> -- 
> Error is
> 
> swanage:~ # fou4s --update
> Getting patch descriptions from rsync://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse
> 10:59:27 URL:http://fou4s.gaugusch.at/patches/ [62/62] -> "index.html" [1]
> 
> Continued download failed on this file, which conflicts with `-c'.
> Refusing to truncate existing file `fou4s-47'.
> 
> 
> FINISHED --10:59:28--
> Downloaded: 62 bytes in 1 files
> swanage:~ #
> swanage:~ # rpm -q wget 
> wget-1.8.2-231

exactly.
this is NOT a fou4s problem.

situation: complete up-to-date file already retrieved,
but client (wget) asked to retrieve (re-get) it, just in case
(that is the wget "-c" option).

as mentioned elsewhere in this thread,
RFC says servers "should" include Content-Length and -Range headers.
which means, it is not required, and clients "should" be able to cope
with it if these headers are not there. 

apache 1 _does_ include these headers,
apache 2 does _not_ .

older clients (wget, curl) relied on the fact that these headers are
present, and think it is a fatal error to get a "range not satisfiable"
report without these headers.

both have been fixed meanwhile.

suggestions:
 1) apache2 servers "should" be modified to include those headers again.
 2) clients "should" be upgraded (or the fix backported) to not choke on
    them being not present

for users (2) is easy: just get the wget-1.9-whatever.src.rpm from suse
9.2, which includes the "client side workaround/fix" and rebuild:

[use your favorite miror]
RPMBUILD=rpmbuild # might be just rpm on the older versions
MIRROR=http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com
wget $MIRROR/suse/i386/update/9.2/rpm/src/wget-1.9.1-50.2.src.rpm
$RPMBUILD --rebuild wget-1.9.1-50.2.src.rpm

(you probably cannot just install the wget binary rpm because iirc
libs have changed from 8.x to 9.2)

(1) should be pretty easy, too, I pointed out where I think the apache
code has to be changed in that other post. only the rfc does say
"should", not "must", so from that pov the server is ok,
and the client is clearly broken... :-)

guess that sums it up.

	lge
--