summaryrefslogtreecommitdiffhomepage
path: root/control/controlhttp/controlhttpserver
diff options
context:
space:
mode:
authorHarry Harpham <harry@tailscale.com>2026-01-08 20:49:18 -0700
committerHarry Harpham <harry@tailscale.com>2026-01-09 12:39:55 -0700
commitf9762064cfcec9ab285750b0e25b48cd31642a31 (patch)
tree114db07b20a1555289cc4d6d26b8d547b18fbf8d /control/controlhttp/controlhttpserver
parent5f34f14e144674a563474b6059ef51a2ee35fd0b (diff)
downloadtailscale-f9762064cfcec9ab285750b0e25b48cd31642a31.tar.xz
tailscale-f9762064cfcec9ab285750b0e25b48cd31642a31.zip
tsnet: reset serve config only once
Prior to this change, we were resetting the tsnet's serve config every time tsnet.Server.Up was run. This is important to do on startup, to prevent messy interactions with stale configuration when the code has changed. However, Up is frequently run as a just-in-case step (for example, by Server.ListenTLS/ListenFunnel and possibly by consumers of tsnet). When the serve config is reset on each of these calls to Up, this creates situations in which the serve config disappears unexpectedly. The solution is to reset the serve config only on the first call to Up. Fixes #8800 Updates tailscale/corp#27200 Signed-off-by: Harry Harpham <harry@tailscale.com>
Diffstat (limited to 'control/controlhttp/controlhttpserver')
0 files changed, 0 insertions, 0 deletions