I have now been able to reproduce the behavior on Windows, with a fake CGI request for an /uv cache hit.
The following commands create a new test repository with an unversioned file, a CGI control file, and set a few environment variables. The commands can be run from a batch file, or by copy-pasting all of them at once into the command prompt. fossil init --admin-user dummy test.fossil fossil rebuild --wal -R test.fossil echo Just a text file> test.txt fossil uv add test.txt --mtime "2018-05-14T00:00" -R test.fossil --user dummy echo repository: test.fossil> test.cfg set SCRIPT_NAME=dummy set PATH_INFO=/uv/test.txt set HTTP_IF_MODIFIED_SINCE= fossil cgi test.cfg echo ==== List SHM and WAL files with HTTP 200 OK ============== dir *-shm *-wal set HTTP_IF_MODIFIED_SINCE=Mon, 14 May 2018 00:00:00 GMT fossil cgi test.cfg echo ==== List SHM and WAL files with HTTP 304 Not Modified ==== dir *-shm *-wal And before each new test run: del test.fossil test.fossil-shm test.fossil-wal With the latest Fossil binary downloaded from fossil-scm.org, the SQLlite temporary files are removed for "200 OK", but they are left behind for "304 Not Modified". With the patch from the first post applied, the temporary files are also removed for "304 Not Modified". --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
