{"version":"2.1.224","anchor":"sandbox-proxy-logs-blocked-requests-and-repairs-lost-request","canonical_anchor":"sandbox-proxy-logs-blocked-requests-and-repairs-lost-request","heading":"Sandbox proxy logs blocked requests and repairs lost request framing","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-proxy-logs-blocked-requests-and-repairs-lost-request","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sandbox proxy logs blocked requests and repairs lost request framing\n\nThe sandbox proxy now logs each denied request with its method, URL and reason.\n\n**What**\n\nThe sandbox's HTTPS proxy now logs each denied request with its method, URL and the reason it was denied, so a blocked network call is traceable rather than silently failing.\n\n**Details**\n\n- The proxy takes a denial callback; the log message is assembled at the time of the denial.\n- When an incoming request has a body but the outgoing headers ended up with neither `content-length` nor `transfer-encoding`, the proxy sets `transfer-encoding: chunked` so the body is still framed correctly.\n- If either side of the connection died while the request filter was running, the proxy now tears the connection down cleanly.\n\n**Evidence**\n\n`onFilterRequestDenied`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}