Re: wget2 | Behaviour difference between wget1 and wget2 for (certain?) web.archive.org URLs (#646)

[Felix Krull (@fkrull)]

Felix Krull commented: 
https://gitlab.com/gnuwget/wget2/-/issues/646#note_1587785605

Thanks for the tip, adding the header makes the downloads work as expected. I'm 
just going to try and get that parameter added to the wget call since it seems 
to be more correct for a pure "download this URL" usecase anyway.

I think you can argue either way whether this is a server issue. The HTML it's 
serving contains an iframe that automagically downloads the file when it's 
opened in a web browser. And from the perspective of the server, wget2 claims 
that it will eat HTML in preference to anything else, so it provides the 
resource in an HTML wrapper suitable for browsers.

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnuwget/wget2/-/issues/646#note_1587785605
You're receiving this email because of your account on gitlab.com.