Re: [Bug-wget] Possible bug with certain error messages being handled as non-error

[Tim Ruehsen]

Hi,

the current version of wget 1.16.3 behaves like this:

$ wget -nv -t 1 --bind-address=123.123.123.123 www.google.com
failed: Cannot assign requested address.
failed: Cannot assign requested address.
failed: Cannot assign requested address.
failed: Cannot assign requested address.
failed: Cannot assign requested address.
failed: Invalid argument.
$ echo $?
4

When using an IP address that is available on my host (and has working routing 
entries), the above command succeeds.

Regards, Tim

On Wednesday 02 September 2015 15:47:03 Christopher 'm4z' Holm wrote:
> Greetings!
> 
> First of all, thanks for maintaining this wonderful software that I've
> been using for years without (code) problems.
> 
> 
> Today however, I noticed wget behaving in a way that seems
> counter-intuitive to me:
> ------------------------------------------------------------ 8<
> ------------------------------------------------------------
> address@hidden:~> wget -t 1 --bind-address=123.123.123.123 www.google.com
> --2015-09-02 15:33:17--  http://www.google.com/
> Resolving www.google.com (www.google.com)... 2a00:1450:400f:805::2004,
> 216.58.209.100
> Connecting to www.google.com
> (www.google.com)|2a00:1450:400f:805::2004|:80... failed: Invalid
> argument.
> Connecting to www.google.com (www.google.com)|216.58.209.100|:80...
> failed: Cannot assign requested address.
> Giving up.
> 
> address@hidden:~> wget -nv -t 1 --bind-address=123.123.123.123 www.google.com
> address@hidden:~> echo $?
> 4
> ------------------------------------------------------------ >8
> ------------------------------------------------------------
> 
> (I'm deliberately trying to bind an IP that is not mine to provoke the
> error.) According to the docs, "-nv" only suppresses non-errors. Are those
> messages not considered errors?