summaryrefslogtreecommitdiffhomepage
path: root/control/controlhttp/controlhttpserver
diff options
context:
space:
mode:
authorAmal Bansode <amal@tailscale.com>2026-01-26 16:41:03 -0800
committerGitHub <noreply@github.com>2026-01-26 16:41:03 -0800
commit6de5b01e04beeb8504c1644e26b7b239a8a12e8c (patch)
treebfbe4e64fb37c383c1c34e0004a93468f3fe59f8 /control/controlhttp/controlhttpserver
parent9385dfe7f654d74c177ffc3e7f4b6fe428562022 (diff)
downloadtailscale-6de5b01e04beeb8504c1644e26b7b239a8a12e8c.tar.xz
tailscale-6de5b01e04beeb8504c1644e26b7b239a8a12e8c.zip
ipn/localapi: stop logging "broken pipe" errors (#18487)
The Tailscale CLI has some methods to watch the IPN bus for messages, say, the current netmap (`tailscale debug netmap`). The Tailscale daemon supports this using a streaming HTTP response. Sometimes, the client can close its connection abruptly -- due to an interruption, or in the case of `debug netmap`, intentionally after consuming one message. If the server daemon is writing a response as the client closes its end of the socket, the daemon typically encounters a "broken pipe" error. The "Watch IPN Bus" handler currently logs such errors after they're propagated by a JSON encoding/writer helper. Since the Tailscale CLI nominally closes its socket with the daemon in this slightly ungraceful way (viz. `debug netmap`), stop logging these broken pipe errors as far as possible. This will help avoid confounding users when they scan backend logs. Updates #18477 Signed-off-by: Amal Bansode <amal@tailscale.com>
Diffstat (limited to 'control/controlhttp/controlhttpserver')
0 files changed, 0 insertions, 0 deletions