{"version":"2.1.224","anchor":"proxy-tears-down-both-sockets-on-a-rejected-request-and-chun","canonical_anchor":"proxy-tears-down-both-sockets-on-a-rejected-request-and-chun","heading":"Proxy tears down both sockets on a rejected request, and chunks bodyless forwards","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/proxy-tears-down-both-sockets-on-a-rejected-request-and-chun","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Proxy tears down both sockets on a rejected request, and chunks bodyless forwards\n\nThe proxy now closes both sockets on a rejected request instead of leaving half-open connections.\n\n**What**\n\nWhen a request is denied or AWS SigV4 re-signing fails, the proxy now destroys the client socket and, if the original socket is a different one, fails that too, instead of leaving a half-open connection.\n\n**Details**\n\n- Separately, if an incoming request declared a body but neither content-length nor transfer-encoding survives into the outbound headers, the proxy sets `transfer-encoding: chunked`.\n\n**Evidence**\n\n`AWS SigV4 re-signing failed: `\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}