PDF page limits for remote reads now come from the connection, and errors quote its cap.
What's wrong with this entry?
Reading a PDF through a remote call no longer checks against one fixed built-in page count. The limits come from the connection the request arrived on, and the error message quotes that connection's own page cap, so different remote setups can return different amounts of PDF.
- Limits used are a per-read page cap and a maximum raw byte size for whole-PDF reads.
- A whole-PDF read is refused only when the whole-PDF byte allowance for that connection is zero.
- Local Read calls are unaffected.
is too many pages to return from this machine in one call
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