The Access-Control-Allow-Credentials HTTP header — cors, declared by 11 providers in the API Evangelist catalog.
Access-Control-Allow-Credentials
CORS IANA permanent response
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
Access-Control-Allow-Credentials is cors — The cross-origin negotiation. A small, closed set of headers that decide whether a browser is allowed to see a response it already received.
The registry
Listed in the IANA HTTP Field Name Registry as a permanent entry. Defined in Fetch.
In the catalog
Declared by 11 providers across 927 published specification files in the API Evangelist catalog, where it appears as a response header — sent by the server.
Governed by these rules
Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.
OpenAPI Components Headers Error error
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Components Headers Info info
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Headers Hyphenated Pascal Case error
HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.
Guidance: Naming →OWASP API8 2023 Define CORS Origin error
Setting up CORS headers will control which websites can make browser-based HTTP requests to your API. The Access-Control-Allow-Origin header should be defined on all responses.
Guidance: Security →