{"version":"2.1.224","anchor":"https-proxy-denials-report-why-and-dead-sockets-are-torn-dow","canonical_anchor":"https-proxy-denials-report-why-and-dead-sockets-are-torn-dow","heading":"HTTPS proxy denials report why, and dead sockets are torn down","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/https-proxy-denials-report-why-and-dead-sockets-are-torn-dow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### HTTPS proxy denials report why, and dead sockets are torn down\n\nBlocked proxy requests now report why, and dead connections are closed rather than written to.\n\n**What**\n\nWhen the proxy's request filter blocks a tunnelled request, it now reports the method, url, reason and the encoded command to the denial handler instead of failing quietly. Once the upstream connection resolves, the socket is destroyed if either end has already gone away, rather than continuing to write to a connection that no longer exists.\n\n**Evidence**\n\n`onFilterRequestDeny`\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}