| Summary: | wget treats 201 as a failure | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | James <neclimdul> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | 1.24.x | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
Some other poor soul on the internet that ran into this. https://dev.openwrt.org/ticket/16885 Fixed in git. Thanks |
Unlink GNU wget, busybox's implementation treats 201 as an error. Logically any 2xx class response would be a success though. Using alpine: # docker run alpine wget BusyBox v1.24.2 (2016-06-23 08:49:16 GMT) multi-call binary. Usage: wget [-csq] [-O FILE] [-Y on/off] [-P DIR] [-U AGENT] [-T SEC] URL... Retrieve files via HTTP or FTP -s Spider mode - only check file existence -c Continue retrieval of aborted transfer -q Quiet -P DIR Save to DIR (default .) -T SEC Network read timeout is SEC seconds -O FILE Save to FILE ('-' for stdout) -U STR Use STR for User-Agent header -Y Use proxy ('on' or 'off') # docker run alpine wget -O - http://192.168.1.202/201.php Connecting to 192.168.1.202 (192.168.1.202:80) wget: server returned error: HTTP/1.1 201 Created Ubuntu 16.04 # wget -q -O - 192.168.1.202/201.php ; echo $? 0