Access-Control-Expose-Headers
IANA permanent
response
2 spellings
Declared by 4 providers across 78 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.
Access-Control-Expose-HeadersACCESS-CONTROL-EXPOSE-HEADERS
The registry
| Status | permanent |
|---|---|
| Reference | Fetch |
Providers declaring it (4)
backpack kore-wireless microsoft-azure newstore