I was coming to the same conclusion, except it appears that IIS has the same problem (judging by what was going on in the IIS WebDAV setup video thread).
Also, if I read the technical docs on Etag, the PUT shouldn't send a new Etag as there is no content in the response (the Etag is tied to the reply content). It looks like the HEAD call does include an Etag, so conceivably issuing a HEAD after confirming the PUT succeeded would get the new Etag. Unfortunately, that would introduce a race condition if there are multiple people editing the file. Does the TiddlyWiki WebDAV saver support anything other than Etag? While it appears Etag is the default, I ran across some cryptic comments about disabling Etag and adding a last-changed timestamp. Possibly the PUT would include the timestamp. Unfortunately, this is not the default for Apache and would require clear documentation on our part to explain to people how to set-up their WebDAV servers (and significantly reduces the likelihood that WebDAV supporting cloud providers will work properly). I've been looking but haven't (yet) figured out how to tell Apache to include the Etag header in the PUT response header. NOTE: to those who have no idea what I was talking about above, Arlen and I are digging into the finer points of the HTTP protocol and WebDAV protocol to see if we can fix an issue that's been bugging us (well, at least me). On Tuesday, September 5, 2017 at 9:18:07 AM UTC-4, Arlen Beiler wrote: > > 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://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/f6fb9358-ef37-419d-882a-71724c99b415%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
