@guille_elia I do see some timeout command line switches that may be useful, but the wget response is a bit confusing to me. It looks like it tries the 192.30… address then it transfers to the 54.231… address and then finally download the file. From start to finish it looks like it took 52 seconds to actually get the file once it was located.
Here are the timeout options with wget. Its not clear in my mind which one is at fault, since I don’t know what the default settings are. But I’m suspecting it was near the 302 redirect message.
-T, --timeout=SECONDS set all timeout values to SECONDS.
--dns-timeout=SECS set the DNS lookup timeout to SECS.
--connect-timeout=SECS set the connect timeout to SECS.
--read-timeout=SECS set the read timeout to SECS.
-w, --wait=SECONDS wait SECONDS between retrievals.
--waitretry=SECONDS wait 1..SECONDS between retries of a retrieval.
--random-wait wait from 0.5*WAIT...1.5*WAIT secs between retrievals.