Content-Range
IANA permanent
response
RFC 9110
2 spellings
Declared by 17 providers across 125 published specification files in the APIs.io network.
A count here is providers whose published contract declares this header — not
providers who send it. Response headers set at the edge rarely appear in an OpenAPI at all, so a low
number can measure documentation practice rather than deployment.
Spelled 2 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
Content-Rangecontent-range
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 14.4: HTTP Semantics |
Providers declaring it (17)
artifactory autodesk-fusion box ebay etsi insforge instabase lakefs microsoft-azure nhost oracle peertube sentinel-hub servicenow supabase the-climate-corporation zededa
Explore
All headers Representation Metadata Guidance on headers.apievangelist.com