Ron: > Someone already made an ETag wrapper for wget: > https://www.w3.org/2001/12/rubyrdf/pack/tests/scutter/wget.pl
Thanks for the interesting link. > There is no requirement or specification for the value of an ETag, > could use the Fossil artifact hash as the ETag value. Then a script > trying to fetch the file can generate the value from the current copy > of the file. I agree, but with the current implementation, at least the <exec-mtime> ingredient is hard to guess for a client script trying to generate a Fossil ETag. I think that the "Last-Modified" header is much easier to handle, as it boils down to parsing a GMT date/time string. And, as already mentioned, clobbering of locally-modified files can be avoided with the timestamp mechanism, this is not possible with an ETag alone. --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
