-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jochen Roderburg wrote: > I did only a few first tests now, because the basic test already had a > problem: > With default options the local timestamps are not set at all. > > Options: no spider, no -O, no content-disposition: > > no timestamping, no local file no HEAD but: local timestamp not set to > remote > no timestamping, local file no HEAD but: local timestamp not set to > remote > timestamping, no local file no HEAD but: local timestamp not set to > remote > timestamping, local file HEAD local timestamp set to remote > > In these cases the HEAD is now used again only for the case where it is > necessary, but the timestamp ...... > One could think that it is now taken only from the HEAD and not from GET.
Hm, that should not be. It should definitely set the timestamp if it gets downloaded... I'll investigate. OOC, was there a specific resource you tested against (just in case I have difficulty reproducing)? - -- 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 iD8DBQFG2xIY7M8hyUobTrERCAQcAJ9ezRd9v+DwE1JuUCVl4bZMswr/NgCdEOTR D2Q9WwL+8HOzWxIizClXTvk= =zNXl -----END PGP SIGNATURE-----
