Referrer Policy specification
E242817
The Referrer Policy specification is a web standard that defines how much referrer information browsers include in requests to enhance privacy and security on the web.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Referrer Policy specification canonical | 1 |
| Referrer-Policy HTTP header | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2174755 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Referrer Policy specification Context triple: [Fetch Standard, integratesWith, Referrer Policy specification]
-
A.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
B.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
C.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Referrer Policy specification Target entity description: The Referrer Policy specification is a web standard that defines how much referrer information browsers include in requests to enhance privacy and security on the web.
-
A.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
B.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
C.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
W3C specification
ⓘ
web standard ⓘ |
| appliesTo |
HTTP requests
ⓘ
document-level policies ⓘ element-level policies ⓘ navigations ⓘ subresource fetches ⓘ user agents ⓘ web browsers ⓘ |
| concerns |
Referer HTTP header
ⓘ
cross-origin request behavior ⓘ downgrade from HTTPS to HTTP ⓘ referrer information in outgoing requests ⓘ |
| defines |
default referrer policy behavior when none is specified
ⓘ
how much referrer information is sent with requests ⓘ interaction between referrer policy and TLS state ⓘ interaction between referrer policy and mixed content ⓘ interaction between referrer policy and navigation requests ⓘ interaction between referrer policy and redirects ⓘ interaction between referrer policy and subresource requests ⓘ mechanism for controlling the Referer HTTP header ⓘ processing model for referrer policies in browsers ⓘ referrer policy values for user agents ⓘ |
| field |
web privacy
ⓘ
web security ⓘ |
| goal |
enhance privacy on the web
ⓘ
enhance security on the web ⓘ limit leakage of sensitive URL information ⓘ provide web developers control over referrer information ⓘ |
| includesPolicyValue |
no-referrer
ⓘ
no-referrer-when-downgrade ⓘ origin ⓘ origin-when-cross-origin ⓘ same-origin ⓘ strict-origin ⓘ strict-origin-when-cross-origin ⓘ unsafe-url ⓘ |
| motivatedBy |
need to prevent leakage of private URL paths and query strings
ⓘ
need to reduce referrer-based tracking ⓘ |
| relatedTo |
Content Security Policy
ⓘ
Fetch Standard ⓘ
surface form:
Fetch specification
HTML Living Standard ⓘ
surface form:
HTML specification
|
| standardizes |
Referrer Policy specification
self-linksurface differs
ⓘ
surface form:
Referrer-Policy HTTP header
referrer policy via meta element ⓘ referrerpolicy HTML attribute ⓘ |
| usedBy |
browser implementers
ⓘ
web developers ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Referrer Policy specification Description of subject: The Referrer Policy specification is a web standard that defines how much referrer information browsers include in requests to enhance privacy and security on the web.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.