An oversized PDF read over a remote connection is refused with a clear explanation.
What's wrong with this entry?
A 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.
- Budgets consulted are the per-read page cap, the whole-PDF raw byte limit and the image raw byte limit.
- A refusal is returned as an invalid-request result rather than as file content.
- Only applies when the read is served over a remote call; local reads are unchanged.
Served whole-PDF read over the transport budget
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
"Did you mean" file suggestions no longer block on a directory scan
Both mention file tool
-
v2.1.242
PDF reads return the document and page images
Both mention file tool
-
v2.1.246
Read separates the file it opens from the file it reports
Both mention file tool