Re: wget2 | Crash downloading file (#632)

[@rockdaboot]

Tim Rühsen commented: 
https://gitlab.com/gnuwget/wget2/-/issues/632#note_1444796603

Interesting that Metalink is still being used. Curl removed metalink support a 
while ago because "It is not used in the real world". So I considered removing 
it as well.

So I think it was not your intention to use Metalink, you just accidentally 
ended up using it !?

In this case, it possibly makes sense to have `--no-metalink` as the default.

Now analysing the Metalink issue... the download might be slow because
 - wget2 has an issue with chunked downloads where chunks are not downloaded in 
parallel
 - the Metalink .meta4 file splits the file into 3039 chunks, not well suited 
for fast internet connections

When downloading the metalink file and starting the download with it, 
everything went well (no crash, file size correct, checksum good).
```
wget2 --no-metalink 
https://download.qt.io/official_releases/qt/6.5/6.5.1/single/qt-everywhere-src-6.5.1.tar.xz.meta4
wget2 --force-metalink -i qt-everywhere-src-6.5.1.tar.xz.meta4
```

But I see that there is an issue... your command line *wrongly* makes wget2 
download with *and* without Metalink in parallel, both jobs writing into the 
same file. This explains the wrong hash.

Note to myself: It may have to do with the 302 redirect.
Looking at the code at a later point in time.

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