{"version":"2.1.246","anchor":"remote-driven-reads-refuse-whole-pdfs-and-cap-page-ranges","canonical_anchor":"remote-driven-reads-refuse-whole-pdfs-and-cap-page-ranges","heading":"Remote-driven reads refuse whole PDFs and cap page ranges","tier":"notice","area":"Remote Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/remote-driven-reads-refuse-whole-pdfs-and-cap-page-ranges","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Remote-driven reads refuse whole PDFs and cap page ranges\n\nReads driven from another session refuse whole PDFs and oversized page ranges.\n\n**What**\n\nWhen a read comes in from another session and the target is a PDF, Read now refuses to return the whole file and refuses over-large page ranges, telling the caller to use `pages` or read the file on the machine where the session runs. It reports error code 16 for those, and error code 15 when a general remote path check fails.\n\n**Details**\n\n- Both refusals apply only when the call carries a remote-call context. Local PDF reads are unchanged.\n- Read also gained a hook that suppresses all permission updates, and now sends an extra classifier field alongside the file path when auto-classifying a call.\n\n**Evidence**\n\n`A whole PDF cannot be returned from this machine to the calling session`\n\n- Area: Remote Execution\n- Names: `pages`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}