bug-wget
[Top][All Lists]
Advanced

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

Re: [Bug-wget] Problem with --content-disposition, HTTP/FTP connection n


From: Jochen Roderburg
Subject: Re: [Bug-wget] Problem with --content-disposition, HTTP/FTP connection not reused
Date: Wed, 19 Oct 2011 10:13:10 +0200
User-agent: Internet Messaging Program (IMP) H3 (4.3.7)

Zitat von Ángel González <address@hidden>:

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





reply via email to

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