Am Freitag, 3. Juli 2015, 18:15:27 schrieb Anthony Bryan: > >> $ wget > >> --input-metalink=http://www.metalinker.org/samples/dsl-3.3.iso.metalink > > I'm not sure what the typical wget user expects, but here are some examples. > > if you keep the current behavior, it might be helpful to print to the > user that they've downloaded a metalink, and how to make wget use it. > > aria2 (another command line metalink downloader) uses these commands > to download the metalink and process it (download the file described > by it & do a hash check) by default. you have to specify > '--follow-metalink=false' to only download the metalink XML file. > > curl on the other hand just downloads the metalink XML file by default > (like any other file), and requires a '--metalink' option to process a > local file or URL. (examples & help/man pages follow)
The above example is not promoted as a metalink file :-(
Wget's behaviour is absolutely perfect in this case:
HTTP/1.1 200 OK
Server: Apache/2.4.12
Last-Modified: Thu, 28 Feb 2013 23:50:21 GMT
ETag: "25d4-4d6d18dc2d087"
Content-Type: application/x-iso9660-image
Accept-Ranges: bytes
Date: Sat, 04 Jul 2015 13:47:34 GMT
Connection: keep-alive
Via: 1.1 varnish
Age: 0
Content-Length: 9684
Only if it were a
Content-Type: application/metalink+xml
or
Content-Type: application/metalink4+xml
the target should be automatically loaded... IMO.
Anthony, why does the server promote the file a x-iso9660-image ?
Is it a bug or a feature ?
Regards, Tim
signature.asc
Description: This is a digitally signed message part.
