Rattledagger <[email protected]> wrote on 06/25/2009 01:08:30 PM:
> Kevin Reed
>
> On Wed, 24 Jun 2009 16:51:09 -0300, you wrote:
> >
> >But it also has this code in file_xfer.cpp (error checking removed to
make
> >email shorter)
> >
> >// for downloads: if we requested a partial transfer,
> >// and the HTTP response is 200,
> >// and the file is larger than it should be,
> >// the server or proxy must have sent us the entire file
> >// (i.e. it doesn't understand Range: requests).
> >// In this case, trim off the initial part of the file
> >
>
> Wouldn't this mean the client already handles this correctly, as long as
WCG
> re-configures their server to ignore the range-request and sends the
> whole file?
>
You are correct. I hadn't tested that setting yet and had instead looked
at the code in the wrong file to see how it would handle the condition if
we were to send the whole file. I have now tested this and BOINC does
handle a full response correctly.>
We have "resolved" this issue by adding the following lines to our
httpd.conf file for the download directory.
RequestHeader unset Range
Header unset "Accept-Ranges"
I scanned our log files for 206 and 416 response codes. It looks like
about 0.2% of our download requests are retries. This will have an effect
on some users, but the vast majority of our files are quite small (less
than 200k after compression) so full re-downloads will not be an
overwhelming.,
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
