Zitat von Jochen Roderburg <[email protected]>:
Zitat von Ángel González <[email protected]>:
Jochen Roderburg wrote:
This looks like the same issue I decribed recently here:
wget makes a HEAD request first, and the reply-headers do not
contain a Content-Disposition header.
The Content-Disposition header comes then on the subsequent GET
request, but wget seems to ignore it there.
Regards,
Jochen Roderburg
Confirmed. Running wget --timestamp -S --content-disposition
http://example.com and giving the Content-Disposition header just
on GET, gives the above result.
Precisely, that is the combination of options which triggers the
effect in recent wget 1.13.x versions because --timestamp=on forces
the HEAD requests.
Older versions with Content-Disposition support (like the 1.11.4
which the OP reported) made *always* HEAD requests with
--content-disposition=on alone and had this error then also always.
Regards,
Jochen Roderburg
Hi Mark,
Just an additional remark what this findings now mean for your
original question: You *can't* avoid the problem with your wget
version 1.11.4, but you usually *can* avoid it with newer 1.13.x
versions.
Regards,
Jochen Roderburg
