Wed 31 Dec 2008 03:29:10 PM UTC, comment #1:
Hi,
I would like to work this out, so could you please assign it to me, thanks!
For debug and test convenience, I wrote a tiny http server, which could output HTTP streams I need. And I tested bug20360 and bug21041 with that tiny server.
For bug20360, it seems that this bug has already been fixed. When HEAD attempt fails for losing connection, Wget could retry HEAD request and GET won't ignore Content-Disposition.
For bug21041, it hasn't been fixed, Content-Disposition is ignored when HEAD attempt fails for unexpected HTTP status code. And I have found the reason.
For bug20658, I think we can add "--content-disposition-headfirst" boolean option to specify HEAD to be sent first. For "--content-disposition" option, only GET will be sent and should carefully terminate connections in response to a last-minute Content-Disposition that indicates we should not download the file.
I think I can fix and test above three bugs, so it would be convenience if admin could assgin all of them to me:-)
Any suggestions are welcome!
|