{"version":"2.1.233","anchor":"gateway-always-sanitizes-400-and-413-errors","canonical_anchor":"gateway-always-sanitizes-400-and-413-errors","heading":"Gateway always sanitizes 400 and 413 errors","tier":"internal","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/gateway-always-sanitizes-400-and-413-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Gateway always sanitizes 400 and 413 errors\n\nSome 400 and 413 responses used to slip through the gateway unsanitized; now they always get cleaned.\n\n**What**\n\nUpstream 400 and 413 responses that carry a recorded message are now always replaced with a sanitized body and copied headers. Previously this rewrite only happened once a capability class had been resolved, so some responses passed through unsanitized.\n\n**Evidence**\n\n`upstream ${e.status} sanitized for CRI caller`\n\n- Area: Gateway\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}