The Public HTTP header — security policy, RFC 2068, declared by 1 providers in the API Evangelist catalog.
Public
Security Policy obsoleted request
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
Public is security policy — Response headers instructing the client to constrain itself — transport security, framing, script sources, sniffing, referrer leakage.
The registry
Listed in the IANA HTTP Field Name Registry as marked obsoleted in the registry — it should not appear in new work. Defined in RFC 2068: Hypertext Transfer Protocol – HTTP/1.1.
In the catalog
Declared by 1 providers across 2 published specification files in the API Evangelist catalog, where it appears as a request header — sent by the client.
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 →