In this case the etag, while basically the same idea, is handled by the browser-side TiddlyWiki and is stored in the pages JavaScript, so it isn't affected by the cache. This problem is usually server-side or disk-side -- its rarely related to the browser.
On Thu, Dec 5, 2019 at 4:25 PM 'Mark S.' via TiddlyWiki < [email protected]> wrote: > After speed-reading wikipedia, it seems to me that if the browser's cache > doesn't update correctly, it might hang on to a 6 hour old etag value. I've > noticed firefox doing this in other capacities. For instance, after > reloading a list of my current reading, items that were previously > unchecked will still show. I will have to load the page a second time in > order to display the correct values. > > On Thursday, December 5, 2019 at 1:11:21 PM UTC-8, Mark S. wrote: >> >> I think I need an explainer about what an "etag" is. There are etags in >> the vim editor, but I don't think you mean the same thing. >> >> Just to repeat. Between one save and a second attempted save was more >> like 6 minutes, not 6 hours. But I don't understand what the etag is and >> how it gets set. >> >> Thanks! >> >> On Thursday, December 5, 2019 at 12:55:52 PM UTC-8, Arlen Beiler wrote: >>> >>> You can disable etag checking completely if you want. If you can include >>> some more examples from the log file that would be great as well. >>> >>> The relevant log file info here shows the two values, ifmatch being the >>> browser copy. The last number is the modified timestamp in milliseconds, >>> which as you can see in this case are 6 hours apart. If you google >>> "epoch converter" you can paste that into "1970 Epoch in Milliseconds" >>> converter to get the date. The third line (and similar lines in more >>> serious scenarios) are debug lines where TiddlyServer points out which >>> parts are different and caused the etag to fail. >>> >>> 412 ifmatch "0-5124547-*1575414313000*" >>> 412 etag "0-5124547-*1575434388000*" >>> *412 caused by difference in modified* >>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1 412 127.0.0.1 >>> /TW2014/T >>> o.html 42.922 ms - - >>> >>> The docs for the putsaver.etag setting is here: >>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#etag-string >>> <https://www.google.com/url?q=https%3A%2F%2Farlen22.github.io%2Ftiddlyserver%2Fdocs%2Fserverconfig.html%23etag-string&sa=D&sntz=1&usg=AFQjCNFwKrGHpGLE1r68GWgYnUkoFBkqmA> >>> >>> The section docs >>> https://arlen22.github.io/tiddlyserver/docs/serverconfig.html#section-putsaver >>> has >>> an example snippet. >>> >>> Alternatively, you can set etagAge (which is seconds, default of 3) to a >>> ridiculously high number (like 2 hours) so it only checks the size and not >>> the timestamp. But remember that the etag is gotten when the file is >>> loaded, so even if it sits in your browser for six hours, it will still be >>> the same if the file has not been modified on disk since then. There are >>> various reasons why this could happen, which is why I added the etagAge >>> setting. Another user had the same problem and we thought it seemed like >>> the antivirus was changing the modified timestamp on certain drives for >>> some reason. >>> >>> Hope that helps. >>> Arlen >>> >>> On Wed, Dec 4, 2019 at 11:07 AM 'Mark S.' via TiddlyWiki < >>> [email protected]> wrote: >>> >>>> Unless my computer has discovered time travel, there is no way the file >>>> on disk is 6 hours newer. >>>> >>>> I load. >>>> I save once. >>>> I do things in the TW >>>> I save again ... and get the error. >>>> >>>> So unless the file was saved with a timestamp 6 hours in the future, it >>>> should be several minutes *older* than the browser version at the time of >>>> the save. >>>> >>>> I'm using 5.1.21 >>>> >>>> I'm wondering why it checks the time at all. Unless I do something >>>> crazy like manually copy a different version to the directory, the browser >>>> version should be "king". >>>> >>>> Perhaps checking the date slows things down. It's noticeably slower >>>> saving a single-file wiki with TS than with BobSaver or file-backups. >>>> >>>> Thanks! >>>> >>>> On Wednesday, December 4, 2019 at 7:19:38 AM UTC-8, Arlen Beiler wrote: >>>>> >>>>> In this particular case, the file on disk is 6 hours newer than the >>>>> copy the browser downloaded. I have not used this feature of TiddlyServer >>>>> much so perhaps I should take a look at it again, but nothing changed >>>>> since >>>>> I made it that I know of. I did run into a scenario where the etag was >>>>> changing by a second or two, so I added the putsaver.etagAge option to set >>>>> the window within which to ignore it. I will check the code to make sure >>>>> everything looks good on my end. What version of TiddlyWiki is the file? >>>>> >>>>> On Tue, Dec 3, 2019 at 11:53 PM 'Mark S.' via TiddlyWiki < >>>>> [email protected]> wrote: >>>>> >>>>>> I get "changed on server" messages regularly. Often on the second >>>>>> time I attempt to save. Talking single files. >>>>>> This didn't happen with the old (1.??) version. It's made it pretty >>>>>> hard to use, since every time it happens I >>>>>> have to do a "rescue" of the changed tiddlers. If it just ignored the >>>>>> non-existent changes on disk and saved >>>>>> it would be fine. Output below. >>>>>> >>>>>> 412 ifmatch "0-5124547-1575414313000" >>>>>> 412 etag "0-5124547-1575434388000" >>>>>> 412 caused by difference in modified >>>>>> [2019-12-03T20:46:07.125-0800] PUT 127.0.0.1 412 127.0.0.1 >>>>>> /TW2014/T >>>>>> o.html 42.922 ms - - >>>>>> >>>>>> Thanks! >>>>>> >>>>>> Just thought I'd take a minute to chime in here. I made TiddlyServer >>>>>>> to solve my own problem of Massive Multi-file Online wikis. It serves >>>>>>> the >>>>>>> folders you specify in a sort of tree allowing them to be grouped >>>>>>> together >>>>>>> and easily navigated with the built-in directory index (even the virtual >>>>>>> directories or "groups"). When a data folder is accessed, TiddlyServer >>>>>>> automatically fires up a node instance of the TiddlyWiki >>>>>>> >>>>>> -- >>>>>> 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 view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/tiddlywiki/febe52b3-ed84-436d-8890-32c56bc766ef%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/tiddlywiki/febe52b3-ed84-436d-8890-32c56bc766ef%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>> 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 view this discussion on the web visit >>>> https://groups.google.com/d/msgid/tiddlywiki/9e5321ed-ad3d-484d-97c4-f192a30c4c10%40googlegroups.com >>>> <https://groups.google.com/d/msgid/tiddlywiki/9e5321ed-ad3d-484d-97c4-f192a30c4c10%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/188ca777-2804-4312-8d75-9cbbcab81de9%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/188ca777-2804-4312-8d75-9cbbcab81de9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSUoQAFnwTawi0%2B79hSRU7%3D%3Dts%3D6gH8woQzdcpxHi%2Bfvg%40mail.gmail.com.
