emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

wget: treat 201,202,203 as success codes too. Closes 9211

Browse Source 
This matches "standard" wget.

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
Denys Vlasenko 2016-08-31 13:28:53 +02:00
parent d811aaa43c
commit 9ff910de6b
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
networking/wget.c
View File

@ -1116,7 +1116,21 @@ static void download_one_url(const char *url)
while (gethdr(sfp) != NULL) while (gethdr(sfp) != NULL)
/* eat all remaining headers */; /* eat all remaining headers */;
goto read_response; goto read_response;
/* Success responses */
case 200: case 200:
/* fall through */
case 201: /* 201 Created */
/* "The request has been fulfilled and resulted in a new resource being created" */
/* Standard wget is reported to treak this as success */
/* fall through */
case 202: /* 202 Accepted */
/* "The request has been accepted for processing, but the processing has not been completed" */
/* Treat as success: fall through */
case 203: /* 203 Non-Authoritative Information */
/* "Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK)" */
/* fall through */
case 204: /* 204 No Content */
/* /*
Response 204 doesn't say "null file", it says "metadata Response 204 doesn't say "null file", it says "metadata
has changed but data didn't": has changed but data didn't":
@ -1141,7 +1155,6 @@ is always terminated by the first empty line after the header fields."
However, in real world it was observed that some web servers However, in real world it was observed that some web servers
(e.g. Boa/0.94.14rc21) simply use code 204 when file size is zero. (e.g. Boa/0.94.14rc21) simply use code 204 when file size is zero.
*/ */
case 204:
if (G.beg_range != 0) { if (G.beg_range != 0) {
/* "Range:..." was not honored by the server. /* "Range:..." was not honored by the server.
* Restart download from the beginning. * Restart download from the beginning.
@ -1149,11 +1162,14 @@ However, in real world it was observed that some web servers
reset_beg_range_to_zero(); reset_beg_range_to_zero();
} }
break; break;
/* 205 Reset Content ?? what to do on this ?? */
case 300: /* redirection */ case 300: /* redirection */
case 301: case 301:
case 302: case 302:
case 303: case 303:
break; break;
case 206: /* Partial Content */ case 206: /* Partial Content */
if (G.beg_range != 0) if (G.beg_range != 0)
/* "Range:..." worked. Good. */ /* "Range:..." worked. Good. */