Andrey Bobelev c4a8c038cd fix: return valid AuthUrl in followup request on expired reg id ... - tailscale client gets a new AuthUrl and sets entry in the regcache - regcache entry expires - client doesn't know about that - client always polls followup request а gets error When user clicks "Login" in the app (after cache expiry), they visit invalid URL and get "node not found in registration cache". Some clients on Windows for e.g. can't get a new AuthUrl without restart the app. To fix that we can issue a new reg id and return user a new valid AuthUrl. RegisterNode is refactored to be created with NewRegisterNode() to autocreate channel and other stuff.		2025-10-11 05:57:39 +02:00
..
debug_test.go	debug: add json and improve	2025-09-09 09:40:00 +02:00
debug.go	debug: add json and improve	2025-09-09 09:40:00 +02:00
maprequest_test.go	state: ensure netinfo is preserved and not removed	2025-09-09 09:40:00 +02:00
maprequest.go	state: ensure netinfo is preserved and not removed	2025-09-09 09:40:00 +02:00
node_store_test.go	state/nodestore: in memory representation of nodes	2025-09-09 09:40:00 +02:00
node_store.go	debug: add json and improve	2025-09-09 09:40:00 +02:00
state.go	fix: return valid AuthUrl in followup request on expired reg id	2025-10-11 05:57:39 +02:00