wget-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

wget2 | Wget / Wget2 differ in behavior of `--content-disposition` (#488


From: Tim Rühsen
Subject: wget2 | Wget / Wget2 differ in behavior of `--content-disposition` (#488)
Date: Wed, 13 Nov 2019 09:34:56 +0000


Tim Rühsen created an issue: https://gitlab.com/gnuwget/wget2/issues/488



>From the IRC / Matrix Wget channel:

`wget --content-disposition 
http://list.iblocklist.com/?list=ydxerpxkpcfqjaybcssw` VS `wget2 
--content-disposition http://list.iblocklist.com/?list=ydxerpxkpcfqjaybcssw`

wget out: `ydxerpxkpcfqjaybcssw.gz`

wget2 out: `index.html?list=ydxerpxkpcfqjaybcssw`

It's a redirection to 
`http://cdn2.iblocklist.com/files/rwxfxfibobsdewqocelx/ydxerpxkpcfqjaybcssw.gz`.
 Wget takes that server-provided name (this might be unsafe), while wget2 
sticks with the original.

Wget2 needs `--trust-server-names` to show the same behavior.

Think it the other way round. Say you want to download 
`http://example.com/archive.tgz` and the redirection goes to 
`http://example.com/jdskdfjksdf?addsfjwer=kdfjhsdkfjksdfj`. Wget2 would still 
save it as `archive.tgz`. Wget would use that other name. What is better then ?

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]