Anti-spam team, Confirmed users
99
edits
User:Apking/Web Security Guidelines: Difference between revisions
Jump to navigation
Jump to search
User:Apking/Web Security Guidelines (view source)
Revision as of 23:33, 27 October 2016
, 27 October 2016formatting
(rough draft) |
(formatting) |
||
| Line 547: | Line 547: | ||
= Referrer Policy = | = Referrer Policy = | ||
When a user navigates to a site via a hyperlink or a webpage includes an external resource, browsers inform these sites of the origin of the requests through the use of the HTTP <tt>Referer</tt> (sic) header. Although this can be useful for a variety of purposes, it can also place the privacy of users at risk. HTTP Referrer Policy is an HTTP header and <meta> tag that allows sites to have fine-grained control over how browsers use the HTTP <tt>Referer</tt> header. For example, if a page at https://example.com/page.html contains this file < | When a user navigates to a site via a hyperlink or a webpage includes an external resource, browsers inform these sites of the origin of the requests through the use of the HTTP <tt>Referer</tt> (sic) header. Although this can be useful for a variety of purposes, it can also place the privacy of users at risk. HTTP Referrer Policy is an HTTP header and <meta> tag that allows sites to have fine-grained control over how browsers use the HTTP <tt>Referer</tt> header. For example, if a page at https://example.com/page.html contains this file <tt><img src="https://not.example.com/image.jpg"></tt>, then the browser will send a request like this: | ||
<pre>GET /image/jpg HTTP/1.1 | <pre>GET /image/jpg HTTP/1.1 | ||