Fixes therealaleph#1022 -- exit-node-routed requests returned raw {s,h,b} JSON to the browser instead of actual page content. Root cause: Code.gs had no raw-return handler. The Rust client sets r:true on the outer Apps Script request to signal verbatim passthrough, but without a matching branch Code.gs was wrapping the exit node's {s,h,b} response in a second {s,h,b} envelope. parse_exit_node_response() peeled one layer and handed the inner {s,h,b} JSON string to the browser as the body. Code.gs (_doSingle): - add req.r === true branch returning resp.getContentText() verbatim via ContentService before the normal {s,h,b} wrap - _buildOpts: followRedirects is now unconditionally true; r controls raw-return mode only, not redirect following domain_fronter.rs (parse_exit_node_response): - scan for \r\n\r\n separator and skip any HTTP framing prefix before JSON parsing; some Apps Script edge nodes prepend HTTP headers to the response body - add content-encoding to SKIP_RESPONSE_HEADERS; exit node fetch() auto-decompresses so forwarding the header causes Content Encoding Error in the browser

Commits

Commits on May 14, 2026

fix(exit-node): fix double-wrapped response envelope in relay path (#1022)

fix(domain_fronter): fix panic from non-char-boundary slice in error paths

Commits on May 15, 2026

fix(pr-review): restored the try/catch in _doSingle, remove EXIT_DIAG debug logging

fix(PR-re-review): removed EXIT_DIAG debug entirely