I've done some pretty thorough testing on this. Where it stands is this: After you save to the Apache (or ISS) DAV, you need to reload the wiki (press browser reload) and you can continue just fine.
*Technical details:* The TiddlyWiki DAV saver uses an HTTP header called eTag. This is a value that indicates the state of the "object" (in this case tiddlywiki file) when it was last received by the browser. When you perform a DAV save operation (a PUT method), the file changed and so the eTag value changed as well. Apache does not set a new eTag value with the PUT operation because Apache cannot confirm that there was no post processing once the file was saved so it does not send an updated eTag until you issue another GET call. This is documented and proper behavior. A PUT is only supposed to send an updated eTag in the response if the server knows that the browser version of the data is the same as the server version. While this can be done with a GET operation, Apache is unable to confirm this with a PUT since Apache is not aware of any post-processing that might happen server-side. I'm still trying to figure out how to force Apache to send an eTag with the response to the PUT, but I haven't yet figured out how. On Monday, October 2, 2017 at 1:31:59 PM UTC-4, Arlen Beiler wrote: > > If using DAV saver, TiddlyServer will prevent overwriting the server with > a stale copy if you are working on more than one device. Apache is supposed > to do this, but we were having trouble with it, so I'm not sure where it > stands. > > Here is the link to the discussion. > https://groups.google.com/d/msgid/tiddlywiki/3206b23b-d4e5-4fe3-8984-70b449b7218c%40googlegroups.com?utm_medium=email&utm_source=footer > > > On Oct 2, 2017 12:57 PM, "Lost Admin" <thelos...@gmail.com <javascript:>> > wrote: > >> If you are going to the extent of putting a server on a Raspberry Pi, why >> not setup a proper web server? Apache with either webdav (for the dav >> saver) or mod_php for the store.php used by tiddlyspot (it's on Github) >> will give you a lot more flexibility. >> >> You can even have ssl/tls if you register a domain. You can use >> Letsencrypt for the certificate for free with readily available scripts. >> >> On Monday, October 2, 2017 at 11:39:44 AM UTC-4, Glenn D wrote: >>> >>> If I want to view and edit from multiple devices would the server be the >>> best implementation? >>> >>> If I install it on my Raspberry Pi, would I be able to edit using >>> TiddlyDesktop on my laptop? Or would it be better to stick w/ TiddlyFox? >>> >> -- >> 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 tiddlywiki+...@googlegroups.com <javascript:>. >> To post to this group, send email to tiddl...@googlegroups.com >> <javascript:>. >> 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/1febf956-0b1d-45ee-82a8-d1582eca44af%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/1febf956-0b1d-45ee-82a8-d1582eca44af%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/f77e11a7-8a98-4b89-aa7b-4d41ae3b8a61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
