I looked at the client code, and (unfortunately) it looks like the client doesn't distinguish between HTTP status 206 (meaning the server returned a partial file) and HTTP status (meaning the server ignored the Range header, and returned the whole file).
(Carl: is this correct?) If this is the case, we need to fix the client so that if it gets a 200 it starts writing the file from the beginning instead of the middle. -- David Kevin Reed wrote: ... > I.e. I should add > > RequestHeader unset Range > > so that apache will not process the range request. However, you can not > set conditions on the RequestHeader like you can with Header so this > would take effect for all download requests (we don't do this for all of > our projects). Any ideas out there? _______________________________________________ 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.
