The
Origin request header indicates where a fetch originates from. It doesn't include any path information, but only the server name. It is sent with CORS requests, as well as with POST requests. It is similar to the Referer header, but, unlike this header, it doesn't disclose the whole path.| Header type | Request header |
|---|---|
| Forbidden header name | yes |
Syntax
Origin: null Origin: <scheme> "://" <hostname> [ ":" <port> ]
Directives
- <scheme>
- The protocol that is used. Usually it is the HTTP protocol or its secured version, HTTPS.
- <hostname>
- The domain name of the server (for virtual hosting) or the IP.
- <port> Optional
- TCP port number on which the server is listening. If no port is given, the default port for the service requested (e.g., "80" for an HTTP URL) is implied.
Examples
Origin: https://developer.mozilla.org
Specifications
| Specification | Comment |
|---|---|
| RFC 6454, section 7: Origin | The Web Origin Concept |
| Fetch The definition of 'Origin header' in that specification. |
Supplants the Origin header as defined in RFC6454. |
Browser compatibility
Update compatibility data on GitHub
| Yes |
12 | 70 | Yes | Yes | Yes | Yes | Yes |
59 | Yes | Yes | Yes |
Legend
- Full support
- See implementation notes.
- User must explicitly enable this feature.
