mirror of
https://github.com/mountain-loop/yaak.git
synced 2026-11-17 22:21:26 +01:00
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>