Document metadata as corpus evidence

See also

Sources

1. 1
   Anthropic documents PDF requirements of a 32 MB maximum request size and a maximum of 600 pages per request, reduced to 100 pages when the request's context window is under 1M tokens.

   PDF support · Before you begin > Check PDF requirements, table · Checked 2026-09-30
2. 2
   Anthropic documents that for PDFs the Claude API web fetch tool returns the content as base64-encoded data and processes it like a directly attached PDF document.

   Web fetch tool · How web fetch works, numbered list item 3 · Checked 2026-09-30
3. 3
   A Webex developer API reference page carries no publication timestamp anywhere in its embedded page state: documentation.entry is null on such a page and the apiReference object that holds its content carries an API version number and no time field.field report

   Reports: Detailed Call History — Get Detailed Call History · documentation.entry and apiReference of the embedded page state · Checked 2026-09-16
4. 4
   All 41 held www.cisco.com sources that the corpus records as reachable returned HTTP 403 to a request carrying a spoofed browser user agent and no other browser headers, and the same URLs return the documents to a request carrying the default curl user agent.field report

   Cisco Preferred Architecture for Webex Calling — Design Overview · HTTP response status for 41 held www.cisco.com source URLs · Checked 2026-09-16
5. 5
   www.cisco.com serves its documentation to a request carrying an ordinary tool user agent such as curl wget or python-requests and to a request carrying a browser user agent together with that browser's accompanying headers, and refuses with HTTP 403 a request carrying a browser user agent and no other browser headers, a Googlebot user agent, or an unrecognised custom user agent.field report

   Cisco Preferred Architecture for Webex Calling — Design Overview · HTTP response status for the document URL under 7 request shapes · Checked 2026-09-16
6. 6
   Every one of the 32 Webex developer documentation guide pages the corpus holds carries a publication timestamp in its embedded page state at documentation.entry.publishDetails.time, an object of time user environment and locale, and the time on a page equals the time carried on that page’s own node in the navigation tree of the same response.field report

   Webex Suite MCP Server · documentation.entry.publishDetails and sideNavigation.sideNavigationData of the embedded page state · Checked 2026-09-16
7. 7
   Two retrievals of the same Webex developer documentation page seconds apart return responses of identical length that differ only in the values of a per-response content security policy nonce, which appears as a csp-nonce meta tag and as a nonce attribute on every script and style element including the one carrying the embedded page state.field report

   Vidcast MCP Server · csp-nonce meta tag and the nonce attributes of the script and style elements of 2 retrievals · Checked 2026-09-16
8. 8
   Cisco serves the Webex Calling article Features available by license type at 2 different help centre addresses carrying different article ids, n1qbbp7 and 0r7a2z, whose rendered article text is byte-identical and whose published date is the same.field report

   Features available by license type for Webex Calling · rendered article text of the 2 addresses compared by hash · Checked 2026-09-16
9. 9
   Five of the 6 records carry a document expiry date already in the past while all 6 are marked active and at version 1.0.

   Cisco Trust Portal document records for the DORA Disclosure type · documentexpiredate documentpublishstatus and documentversion fields · Checked 2026-09-05
10. 10
    Webex developer documentation pages carry a publication timestamp in the embedded page state at documentation.entry.publishDetails.time, an ISO 8601 value that differs between pages fetched in one pass: the webhooks guide reads 2026-09-10, and the provisioning and integration scopes guides read 2026-08-13.field report

    Webex for Developers — Webhooks · documentation.entry.publishDetails.time of the webhooks provisioning and integration scopes guides · Checked 2026-09-16

Documents

Cite this page

WarmTransfer. (2026, September 30). Document metadata as corpus evidence. WarmTransfer. https://warmtransfer.net/knowledge/cisco-doc-metadata-as-evidence

@misc{warmtransfer-cisco-doc-metadata-as-evidence,
  title  = {Document metadata as corpus evidence},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/cisco-doc-metadata-as-evidence},
  note   = {Verified 2026-09-30}
}