Re: Bug-wget Digest, Vol 188, Issue 6

[David Niklas]

On Sat, 8 Jun 2024 13:28:08 +0200
Tim Rühsen <tim.ruehsen@gmx.de> wrote:
> On 6/4/24 21:28, David Niklas wrote:
> > I understand why wget2's behavior is different. There are use cases
> > for it. I'm open to the new behavior, provided that there is some way
> > to follow the original behavior.
> > 
> > The arguments for the wget1's behavior are (in no particular order):  
> 
> <...>
> 
> I think your arguments are correct.
> A new option to switch the behavior back to wget1 would be fine, maybe 
> even make it the default behavior.
> 
> https://gitlab.com/gnuwget/wget2/-/issues/668

Thanks!

> >>   > What does "Adding URL: $URL" mean?  
> >>
> >> It means that a URL has been found and it now is checked whether it
> >> will be enqueued into the list of to-be-downloaded URLs. These
> >> checks are e.g. if the URL is parsable/valid, has a known scheme
> >> (HTTP or HTTPS), isn't already known, matches filters etc. One of
> >> the next lines will tell you whether the URL was actually enqueued
> >> or whether it has been sorted out (the reason is given as well).  
> > 
> > I'd prefer it if wget2 wasn't so chatty. Knowing what is DL'ed is
> > useful, what's enqueued is okay-ish, but when wget2 starts listing
> > off every URL it's found I find it to be too verboten IMHO.  
> 
> I am open to changes here, this is not set in stone.

I'm tempted to offer to make these 2 changes myself, but I've not signed
any GNU copyright release form thing yet and, because I'm a student, I'd
basically only be able to contribute a small change here or there.

What do you think?

> > I tried -nv, but it's really quiet. Though it does give a reason, it
> > doesn't list HTTP response codes for failed requests. E.g.
> > 
> > Failed to open web.archive.org/web/index.html
> > web.archive.org/web/index.html not found (2)
> > 
> > While I'm at it, what does "(2)" mean?  
> 
> That is the errno value that was set when some function (like open()) 
> returned an error.
> 
> There are different tools to convert this into text (e.g. "errno" from 
> the debian moreutils package).
> 
> $ errno 2
> ENOENT 2 No such file or directory
> 
<snip>

Ah, that makes sense and, like http return codes, it's easy enough to
understand/decode.

Thanks,
David