Thinking about HTTP caching twice, the following comes to my mind: A command line download tool, that unlike a web browser does not keep a cache of content and associated ETags, won't be able to calculate the ETag for a file it is going to request from a Fossil web server.
ETags are not simple file checksums, and Fossil seems to use the following information to generate them: <mask><exec-mtime>/<data-or-config-key>/<cookie>/<hash> So command line download tools can only rely on the "Last-Modified" header. And, as already mentioned, I do see additional benefit from receiving file timestamps over the web. This is in contrast to check-out timestamps, which Fossil does not preserve, likely so that build tools like `make' know what to do. --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
