Minimal, and reliable test case: 1) Set-up a WebDAV server on Apache (follow the Apache instructions, nothing special).
2) Put a TiddlyWiki on it. Also nothing special, just the standard empty.html from TiddlyWiki.com. 3) Edit a Tiddler and save it (make sure it saves to the WebDAV server. 4) Wait for the save to finish. 5) Make another edit (of the same tiddler if you want) 6) Save again. 7) The error pops up. In Firefox the developer tools can be used to see what is passing on the network. Pay close attention to the ETAG header and it's value (and when it doesn't show up). In theory you could do this with Chrome too, but when I try the Chrome developer tools keep hanging so I can't see the headers on each step. Judging by what is going on in the IIS thread, I think IIS has the same issue. On my Lighttpd server, I don't have this issue. On Tuesday, September 5, 2017 at 1:12:06 PM UTC-4, PMario wrote: > > On Tuesday, September 5, 2017 at 3:46:50 PM UTC+2, Lost Admin wrote: >> >> 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). >> > > Is there a minimal test-case? So I can reproduce the issue? > > >> 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. >> > > WebDAV supports a locking mechanism. ... It could be used to prevent 2 > users editing a TW at the same time. > Yes, that is sort of the problem. the mechanism to prevent the editing conflicts is handled by the ETAG header. But, when you save changes (HTTP PUT), you don't get a new ETAG with the response from Apache. However, the ETAG changes whenever the file changes. At least, I *think* that is what is going on. -- 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/1ebffb7b-86a0-4b39-9172-f562bd559091%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
