It is becoming pretty clear that for some reason the Etag is not being set in the response header, nor anything else equivalent to it. Per our discussion privately, it does seem that this is an Apache issue, however I have not been able to look into it further.
A couple of articles which touch on this: - https://fullstackhack.wordpress.com/2014/12/10/the- pain-of-etags-mod_deflate-apache-2-4-and-tomcat-7/ <https://fullstackhack.wordpress.com/2014/12/10/the-pain-of-etags-mod_deflate-apache-2-4-and-tomcat-7/> - https://httpd.apache.org/docs/2.4/caching.html At some point I will test it on one of my servers and see if I can get it working. However, it is obvious that this is the problem. One option would be to make a second head request if the 204 response does not contain an Etag, but I guess that wouldn't be atomic either. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSKxwo4OqO5Z127uob_JKaWsT69ibBXyvc6s92fvT72hg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
