{"version":"2.1.248","anchor":"oversized-served-pdf-reads-are-refused-with-a-clear-reason","canonical_anchor":"oversized-served-pdf-reads-are-refused-with-a-clear-reason","heading":"Oversized served PDF reads are refused with a clear reason","tier":"notice","area":"File Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/oversized-served-pdf-reads-are-refused-with-a-clear-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Oversized served PDF reads are refused with a clear reason\n\nAn oversized PDF read over a remote connection is refused with a clear explanation.\n\n**What**\n\nA Read of a PDF that arrives over a remote connection is now checked against that connection's size budgets, and one that exceeds them comes back as an explicit refusal with an explanation instead of an oversized payload.\n\n**Details**\n\n- Budgets consulted are the per-read page cap, the whole-PDF raw byte limit and the image raw byte limit.\n- A refusal is returned as an invalid-request result rather than as file content.\n- Only applies when the read is served over a remote call; local reads are unchanged.\n\n**Evidence**\n\n`Served whole-PDF read over the transport budget`\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}