-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Alex Owen wrote: > Hello, > > If i run : > wget http://server.domain/file > > How can I differentiate between a network problem that made wget fail > of the server sending back a HTTP 404 error? > > ( I have a use case described in debian bug http://bugs.debian.org/422088 ) > > I think it would be nice if the exit code of wget could be inspected > to determin if wget failed because of a 404 error or some other > reason.
Hi Alex, We do plan to look evaluate differentiation of exit statuses at some point in the future; however, it's not one of our very highest priorities for the moment, and it's currently targeted for Wget 1.13 (the bug report is at https://savannah.gnu.org/bugs/index.php?20333, but there's really not much description there). We are about to release Wget 1.11, hopefully within a month. It is possible that this item will be targeted for a sooner release, in Wget 1.12; mostly it just needs a final agreement on how exit codes should be divided, which means discussion. Actual implementation will be trivial. But, in the meantime, I'm not sure I want to introduce different exit codes on an individual basis. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG6aGF7M8hyUobTrERCO03AJ9FllUtvfZf3+aUX0a+PP1h5EBILgCdEwj8 yDjpiVmkBf/3OQ2IRSILCTs= =BVBE -----END PGP SIGNATURE-----