{"version":"2.1.248","anchor":"pdf-page-limits-for-remote-reads-now-depend-on-the-connectio","canonical_anchor":"pdf-page-limits-for-remote-reads-now-depend-on-the-connectio","heading":"PDF page limits for remote reads now depend on the connection","tier":"notice","area":"File Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/pdf-page-limits-for-remote-reads-now-depend-on-the-connectio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### PDF page limits for remote reads now depend on the connection\n\nPDF page limits for remote reads now come from the connection, and errors quote its cap.\n\n**What**\n\nReading 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.\n\n**Details**\n\n- Limits used are a per-read page cap and a maximum raw byte size for whole-PDF reads.\n- A whole-PDF read is refused only when the whole-PDF byte allowance for that connection is zero.\n- Local Read calls are unaffected.\n\n**Evidence**\n\n`is too many pages to return from this machine in one call`\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}