HTTP Content-Range Response Audit API Audit supplied Content-Range occurrences and a single-part response-body length without contacting a server.
Audit supplied Content-Range occurrences and a single-part response-body length without contacting a server. Supply requestMethod GET and responseStatus 206 or 416; multipart 206 bodies are outside this profile. Preserve every original occurrence in contentRangeValues, including empty values; an empty array means absent. Supply observedRepresentationBodyOctets as a nonnegative decimal string, or null when unmeasured. For a 206 response, count the representation-data octets carried in the selected response body after removal of transfer framing and before content decoding, so the count addresses the same encoded representation as Content-Range. The report checks last >= first, known complete length > last, and selected length last - first + 1. Decimal positions, lengths and calculations use exact integers, including values beyond JavaScript safe integers; normalized results are decimal strings and original lexical evidence remains unchanged. A 416 bytes */total reports the complete representation length; any supplied error-body octet count is retained but never compared with that length. Absence on 416 emits a recommendation finding because RFC 9110 uses SHOULD rather than an unconditional MUST. Surrounding OWS is interpreted without changing the supplied evidence. Other range units are unsupported-profile; duplicate, empty, malformed and status-incompatible values are separate findings. Field input accepts HTAB and visible ASCII only; CR, LF, other controls and unsupported characters are rejected by schema. This bounded RFC 9110 sections 14.4, 15.3.7 and 15.5.17 audit does not validate a complete response, original Range request, multipart body, server, authorization, representation identity or transfer. It does not certify server conformance. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.
Agent API guide → · Website orders show the report on your private order page.
Your input · JSON Load a small example The complete checkout request must fit within 40,000 UTF-8 bytes. Your input is validated again before an order is created.