-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrea Grillini wrote: > Micah Cowan wrote: >> This should really, really not be the case. Please provide more detailed >> information and reproducible examples. Also, what version of Wget are >> you running, and on what OS? > > I use wget 1.11.4 on Linux Ubuntu 9.10 Netbook Remix. > > The URL called includes a php script and a couple of parameter-value > pair (I suppose a path and a file name). For the moment I avoid passing > the URLs directly, it's a matter of non-free videoclips available for > download for a limited time. But I can pass the header of the one of the > HTTP responses. > > ----------------------------------------------------------- > > 200 OK
<snip> > Content-Length: 58430011 This response indicates that the server declined to send wget a "continuation" of the existing files; can you send the request headers that corresponded to this response? Also, please show the full invocation, as much as you're able without divulging sensitive information. And please keep the list Cc'd, for general edification. Can you re-verify that wget really does behave differently on URLs specified on the command-line versus other sources? If you could provide (edited) request headers corresponding to those two cases, that would be very helpful (wget will spew them out if you give it the --debug flag). - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. Maintainer of GNU Wget and GNU Teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkscmGAACgkQ7M8hyUobTrH/ugCeP2gJ/6hevWH2YNGFCTs9+9eQ qw0AnjLoKyZteTr1FHBMk0ufR8GiswHj =XrHQ -----END PGP SIGNATURE-----
