-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jochen Roderburg wrote: > Zitat von Micah Cowan <[EMAIL PROTECTED]>: > >> Hm... that change came from the Content-Disposition fixes. I'll investigate. >> > > OK, but I hope I am still allowed to help a little with the investigation ;-)
Oh, I'm always very, _very_ happy to get help. :D > I made a few more tests and some debugging now and I am convinced now that > this > "if send_head_first" is definitely the "immediate cause" for the new problem > that the remote timestamp is not picked up on GET-only requests. <snip> > Btw, continued downloads (wget -c) are also > broken now in this case (probably for the same reason). Really? I've been using this Wget version for a bit, and haven't noticed this problem. Could you give an invocation that produces this problem? > I meanwhile also believe that the primary issue we are trying to repair (first > found remote time-stamp is used for local and not last found) has always been > there. Only a year ago when the contentdisposition stuff was included and more > HEAD requests were made I really noticed it. I remember that it had always > been > more difficult to get a newer file downloaded through the proxy-cache when a > local file was present, but as these cases were rare, I had never tried to > investigate this before ;-) I'm not surprised to hear this; it didn't look like it had ever been working before... and it's not a common situation, so I'm not surprised it wasn't caught earlier, either. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG49HJ7M8hyUobTrERCJvXAJ0QHN8/8e9EcWUFV10RIWOIisRrnwCggzqI 62SZmq7si3/p3be41IVIjj0= =TBid -----END PGP SIGNATURE-----
