Content-Range
Declared by 26 providers across 319 published specification files in the APIs.io network.
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 (26)
acronis adobe-suite artifactory autodesk-fusion bonitasoft box ebay etsi insforge instabase lakefs magic-moment microsoft-azure nasuni nhost oracle oracle-cloud oracle-platforms peertube progress-software red-hat-ansible-automation-platform sentinel-hub servicenow supabase the-climate-corporation zededa
Explore
All headers Representation Metadata Guidance on headers.apievangelist.com
Work with this as data
Every header here is available over the APIs.io API and to AI agents over MCP. HTTP Headers is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.