tailscale/control/controlclient
Anton Tolchanov 958bcda5bf control/controlclient: handle 429 responses during node registration
If we get a 429 response during node registration, use the `Retry-After`
header for backoff instead of the regular exponential backoff.

The rate limiter error is propagated to the user, just like other
registration errors are, e.g.

```
$ tailscale up
backend error: node registration rate limited; will retry after 57s
exit status 1
```

Updates tailscale/corp#39533

Signed-off-by: Anton Tolchanov <anton@tailscale.com>
2026-04-15 18:54:08 +01:00
..
auto.go control/controlclient: handle 429 responses during node registration 2026-04-15 18:54:08 +01:00
client.go control,health,ipn: move IP forwarding check to health tracker (#19007) 2026-03-18 16:24:12 -04:00
controlclient_test.go control/controlclient: handle 429 responses during node registration 2026-04-15 18:54:08 +01:00
direct_test.go control/controlclient: handle 429 responses during node registration 2026-04-15 18:54:08 +01:00
direct.go control/controlclient: handle 429 responses during node registration 2026-04-15 18:54:08 +01:00
errors.go all: remove AUTHORS file and references to it 2026-01-23 15:49:45 -08:00
map_debug.go control/controlclient: add patchify miss stats 2026-04-15 08:05:57 -07:00
map_test.go control/controlclient: add patchify miss stats 2026-04-15 08:05:57 -07:00
map.go control/controlclient: add patchify miss stats 2026-04-15 08:05:57 -07:00
sign_supported_test.go all: remove AUTHORS file and references to it 2026-01-23 15:49:45 -08:00
sign_supported.go all: remove AUTHORS file and references to it 2026-01-23 15:49:45 -08:00
sign_unsupported.go all: remove AUTHORS file and references to it 2026-01-23 15:49:45 -08:00
sign.go all: remove AUTHORS file and references to it 2026-01-23 15:49:45 -08:00
status.go all: remove AUTHORS file and references to it 2026-01-23 15:49:45 -08:00