{"version":"2.1.229","anchor":"oversized-requests-get-their-own-log-line","canonical_anchor":"oversized-requests-get-their-own-log-line","heading":"Oversized requests get their own log line","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/oversized-requests-get-their-own-log-line","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Oversized requests get their own log line\n\nRequests rejected for being too large now get their own clearly labelled error log line.\n\n**What**\n\nServer rejections for a request that is too large are now logged at error level under their own branch, next to the existing content-filtered and credential-error cases, so they are distinguishable in logs.\n\n**Evidence**\n\n`API request_too_large: `\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}