> One possible solution may be to include the "cexpire" field in > ETag calculation, drop the If-Modified-Since handler, but still > return a Last-Modified date.
Well, it may be possible to support both caching mechanisms. But then an ETag mismatch should result in a cache miss, and the If-Modified-Since route should no longer be taken thereafter. As Fossil supplies both and ETag and a Last-Modified header for the initial (non-cached) page view, web browsers will also send back both headers, and then If-Modified-Since can undermine If-None-Match cache misses. --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
