Sorry for spamming the list, I try short. Just another comment about Fossil's If-Modified-Since rules:
http://fossil-scm.org/index.html/artifact?name=535a623ccd&ln=154-157 I learned a lot about If-Modified-Since when adding HTTP caching to my home-brewed wiki. All kind of information was important to compute the Last-Modified header, like the last modified time of the most recent page in the wiki (to decide whether or not to expire a page, and reparse its hyperlinks, as they were styled differently when targeting existing or missing pages), the user login time (to decide whether or not to expire a page, if another user with different permissions was logged in), or the CGI script last modified time (to expire pages rendered with an earlier version of the script, mostly useful for developing and testing) -- but the "real" modified time of the wiki page itself was not used. That's the principle Fossil uses when serving "processed" unversioned content (such as wiki pages, where the output may change with new versions of Fossil with enhanced wiki rendering capabilities, or with the menu bar entries reflecting permissions of the currently logged-in user). The Last-Modified header of an unversioned file is not important, in this case, and can never be older than the Fossil binary file mtime. But for binary files, such as zip-archives, I see the /uv web page more as a "static" store, and would like to get the "real" Last-Modified header, so that (simple) scripts can decide whether or not a re-download is necessary, and apply correct time stamps to the downloaded files. Maybe Fossil could treat "processed" content (wiki pages and the like) differently from purely "static" content? Or, an additional /uvraw (or /static) web interface could be used to download unprocessed content, as is, with the original Last-Modified time stamps? Is this the famous 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors? :) (I'm just trying to be funny, I hope my amateurish messages are not offending to all you highly decorated computer specialists. Also, I can't reproduce the leftover SHM and WAL files on Windows, and I'm not able to build Fossil for FreeBSD and do more tests there, my shared host is lacking tools, and I don't have my virtual machine "at hand", right now, I'm sorry.) --Florian _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
