/token in sync URI on Firefox Nightly for Android

[bcspragu]

Hi there!

I just replaced my old self-hosted sync server (the Python one) with this new one, backed by Postgres. I ran into a few issues that I got sorted out, and just documenting them here in case anyone else hits these:

1. Needed to set X-Forwarded-Proto: https in my reverse proxy - I don't actually know if this is required or not, but desktop Firefox was failing to sync with 404 errors IIRC, and after I added the header, everything was syncing successfully. In Caddy, the config looks something like this:

<your sync server> {
	reverse_proxy <local sync server address> {
		header_up X-Forwarded-Proto "https"
	}
}

2. Stripping /token on mobile Firefox - Even after I got desktop working, Android Firefox Nightly (version ~150.0) was failing to sync. Running adb logcat, I was able to see it was getting a 404 trying to hit /token/1.0/sync/1.5. I had definitely set the URL correctly following the official instructions, so I don't know if this was a caching bug or something else going on, but I restarted Firefox and the phone several times, triple checking that I had configured the URL to <sync server URI>/1.0/sync/1.5, so I decided to "fix it in post" with my reverse proxy, which looked something like this in Caddy:

<your sync server> {
	handle_path /token/* {
		reverse_proxy <local sync server address> {
			...
		}
	}

	...
}

Which basically says "strip the /token/ prefix from the URL and forward it to the backend. So <host>/token/test would go to the backend with the path re-written to /test. Once I deployed this change, mobile sync started working immediately (as noted by both server and client logs, as well as manually checking Postgres)

I don't know if there are one or more bugs here, or if this is user error on my part, but it works now so that's fun!

[HorlogeSkynet]

Hello @bcspragu !

'just performed the very same migration as you, and I second your 1-st points !

However, I can confirm instructions are correct even for "Mobile" Firefox : once I've stripped /token from custom sync server URL and pressed "Stop Firefox" to apply it, it worked OOTB without making the reverse proxy stripping it itself.
No, you were right. It looks like /token is still appended to requests by FF for Android. I also had to tweaked reverse proxy to keep synchronization working.

(syncstorage-rs v0.22.2 / Fennec v148)

Bye ! 👋