Chris Dunkle wrote:
Wget developers,
This may not be considered a bug, but it is unexpected behavior for me,
and thus I'm reporting it here. I'm using GNU Wget 1.10.2 with the
following options:
wget -r -x -p --save-headers 192.168.0.1
The web server requires a username and password for the default page,
and thus I receive a 401 Unauthorized response. I would expect that the
HTML data that was returned, including the HTTP headers, would be saved
in the file 192.168.0.1/index.html. But instead, there are no files
written, and the directory isn't even created. In most cases, it would
make sense that nobody would want to save this data, so I can understand
this behavior. But I would like to save whatever data is returned to me,
even if it may not be what I'm expecting. I'm receiving the same results
for a 403 Forbidden response, and this is probably the case for other
ones as well. The 401 outputs "Authorization failed." and the 403
outputs "xx:xx:xx ERROR 403: Forbidden." after execution.
Would this be considered a bug, or is this just an undocumented feature?
If it's not considered a bug, could a command line option be added that
saves the data from 4xx error code responses rather than just quitting?
Basically, if the connection is successful, and something is returned, I
want to keep it, no matter what it is.
hi chris,
wget currently does not save error messages. i am not sure if such a
feature would be actually useful for our users, and i am not very keen
on adding another very-rarely-used feature to wget.
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi http://www.tortonesi.com
University of Ferrara - Dept. of Eng. http://www.ing.unife.it
GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget
Deep Space 6 - IPv6 for Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
