{"version":"2.1.224","anchor":"proxy-survives-malformed-requests-and-broken-sockets","canonical_anchor":"proxy-survives-malformed-requests-and-broken-sockets","heading":"Proxy survives malformed requests and broken sockets","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/proxy-survives-malformed-requests-and-broken-sockets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Proxy survives malformed requests and broken sockets\n\nThe sandbox proxy no longer crashes on malformed requests or broken sockets.\n\n**What**\n\nThe local sandbox proxy now attaches error handlers to client requests, responses and upstream responses, so a stream error is logged instead of crashing it. Malformed client requests get 431 Request Header Fields Too Large when headers overflow and 400 Bad Request otherwise, then the socket is destroyed after a one second timer that does not hold the process open.\n\n**Evidence**\n\n`431 Request Header Fields Too Large`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}