"TypeError: etag is null" when logged in running and running via Node.js in Firefox

[Jack Baty]

I've decided to go back to running TiddlyWiki via Node.js on the server. I've been running locally with Node for a while, so I simply copied the entire wiki folder to the server and configured the web server (Caddy) as a reverse proxy. (https://rudimentarylathe.org)

I'm using the following config to start the service...

forever start --spinSleepTime 10000 /usr/local/bin/tiddlywiki /home/jbaty/apps/wiki --listen "readers=(anon)" writers=jack username=notmyusername password=thisisnotmyrealpassword

Everything seems to work ok when I'm accessing the site anonymously, but once I log in (using Firefox) I get the big red JavaScript error modal with the following:

TypeError: etag is null

This does not happen in Safari. I've disabled any Firefox extensions  that might tamper with the requests, and I've also turned of Firefox's "Enhanced Tracking Protection" for the domain, just in case.

Any idea why I might be seeing this?

Node 14.x

TiddlyWiki 5.1.22

Latest Firefox.

Thanks!

Jack

[Jack Baty]

Other notes: The cloud icon remains red with the syncing animation running continuously. Choosing logout from the menu returns a 404 message.

[HokieGeek]

Jack,

I just encountered this too. For me the issue was with the ClearURLs add-on https://addons.mozilla.org/en-US/firefox/addon/clearurls/. Once disabled it, the problem went away. If you don't have that add-on, I would suggest opening the wiki in Private mode and if the issue doesn't replicate in that mode, then start disabling add-ons in regular mode until it goes away.

[Jack Baty]

I do have the ClearURLs extension! Funny, I never think of disabling that one when troubleshooting for some reason.

Trouble is, I've moved the wiki in question back to a single HTML file so I don't have a good way to confirm the fix for me. Thanks for letting me know!

[HokieGeek]

Fair nuf. For anybody else finding this thread, looks like you just have to turn off the ETag filtering option instead of disabling the whole thing. Would be nice if the add-on had a whitelist.