Hi Jochen, before my change, the HEAD request was done every time --content-disposition was specified.
Other cases where HEAD is really needed must work as before, if they don't then it is a bug. Thanks for the information, I am going to check it right now. Giuseppe Jochen Roderburg <[email protected]> writes: > Hi Giuseppe, > > There has been been a recent change in the 1.12.1 development version > which is described as: > > Do not use an additional HEAD request when --content-disposition is used, > but use directly GET. > > This "additional HEAD request" used to be in wget for the cases where > it needs additional information from the HTTP headers to decide if it > really needs to do a GET (e.g. Date-Modified). > > Can you explain how these cases are handled now after this change? > I understand that wget also gets the HTTP-Headers as reply to the GET, > but what does it do now when it finds out that a download is not > necessary? How does it stop the subsequent data-transfer? > > I ask this because after this change I observed significant random > delays on my daily wget downloads (summing up to several hours ;-) in > a certain complicated situation involving a proxy. > > Best regards, > > Jochen Roderburg > RRZK > University of Cologne > Robert-Koch-Str. 10 Tel.: +49-221/478-7024 > D-50931 Koeln E-Mail: [email protected] > Germany
