The plain HTTP client used hyper's own connector on Linux and Windows,
which tries the other address family 300 ms in. Connecting through the
dial lost that, so a host with a broken IPv6 route took five seconds to
reach over IPv4. Plain HTTP now races the families the same way, within
the same 10 second budget; a CONNECT still dials its addresses in turn.
The timeout test no longer depends on how the network treats a
documentation address.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A plain HTTP request whose server can't be reached (the name doesn't
resolve, the port is closed, the host or network is unreachable, or
it times out) no longer gets a 502 page the engine made up. The
client's connection is reset unanswered, so the browser or app shows
its own connection error, as it would with no proxy, and the flow ends
as an error with the same plain reason a failed CONNECT gets.
The plain HTTP client now connects through the CONNECT dial, so it
shares its 10 second budget and its failure reasons. On macOS, when
Network.framework falls back to a local system proxy, the real cause
is found by looking the name up apart; the fallback wording goes to
the debug log only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The engine now opens the TCP connection to a CONNECT's server before it
answers. When the server can't be reached, the CONNECT gets a 502 (or a
504 on a timeout) and the client reports its own connection error, rather
than a 200 followed by a 502 inside the decrypted session or a silent
hang-up in a tunnel. The failure is recorded as one error flow.
The dialled connection is handed to the tunnel, or to the first upstream
connection of a decrypted one, so nothing is dialled twice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Apply the approved wording table: labels stay short, explanations are one
full sentence about the user's traffic, and detail moves behind an info
icon on the first-run card, the body banners, the Settings Helper row and
the rejected card. One word per thing: traffic and flows, recorded,
truncated, domains, searches, the CLI, Retry.
Backend messages that reach the window change with them, with the tests
and harness fixtures that assert on the old text. The two working files
for the pass are removed from the branch.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
CVE-2026-111497 is an out-of-bounds write in the Brotli decoder. It
reaches Yaak through the bundled Node (`yaaknode`, used by plugins) and
through the pure-Rust `brotli-decompressor` that yaak-http uses to decode
`br` responses.
- Bump the plugin runtime Node from 24.11.1 to 24.22.2 and update the
vendoring script's SHA256 pins from the signed SHASUMS256.txt.
- Move yaak-http from `brotli = "8"` to `brotli = "9"`, locking brotli
9.1.1 and brotli-decompressor 6.2.0.
Tauri's pinned git rev still pulls brotli 8.0.1 and brotli-decompressor
5.0.0 for its embedded-asset compression; that needs a Tauri bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Rebuild a bare-path plain-HTTP request's URL from Host, answer 400
"no host in request" when there is none, and refuse with 508 a rebuilt
request that is routed back into the proxy, which would otherwise loop
without end.
- Drop Host when forwarding to an HTTP/2 upstream. Google's servers reset
every stream that carries Host alongside :authority.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>