Content-Location
IANA permanent
response
RFC 9110
reached by regulation
2 spellings
Declared by 11 providers across 215 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-locationContent-Location
Reached by regulation
Basis: mandated.
The law, or a technical standard the law makes binding, names this header.
Visible in a published contract, which is what is counted here.
cms-interoperability-prior-authorization
Carried by the fhir-bulk-data standard.
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 8.7: HTTP Semantics |
Providers declaring it (11)
athena-health benchling brale cms-gov elbo-ai-inc jefferson-health oracle smarthealthit snyk temple-health transifex
Explore
All headers Async & Long-Running Guidance on headers.apievangelist.com