The check for that content-range is received must only be made if we requested

GET resume. Other resumes are upload-wise and don't care about this header
in the download stream
This commit is contained in:
Daniel Stenberg 2001-01-26 15:50:56 +00:00
parent 3a3f632bf0
commit c331ef02f9
1 changed files with 7 additions and 3 deletions

View File

@ -444,10 +444,14 @@ _Transfer(struct connectdata *c_conn)
write a chunk of the body */
if(conn->protocol&PROT_HTTP) {
/* HTTP-only checks */
if (data->resume_from && !content_range ) {
if (data->resume_from &&
!content_range &&
(data->httpreq==HTTPREQ_GET)) {
/* we wanted to resume a download, although the server
doesn't seem to support this */
failf (data, "HTTP server doesn't seem to support byte ranges. Cannot resume.");
doesn't seem to support this and we did this with a GET
(if it wasn't a GET we did a POST or PUT resume) */
failf (data, "HTTP server doesn't seem to support "
"byte ranges. Cannot resume.");
return CURLE_HTTP_RANGE_ERROR;
}
else if (data->newurl) {