Everything, Everything

2020: J F M A M J J A S
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Referrer Policy
Monday 13th March, 2017 09:09 Comments: 0
I recently discovered that there's a new HTTP header that's worth setting. There's a good explanation about the Referrer Policy header by Scott Helme, and there are further details here.

This allows you to carefully control what information is sent by the browser when you browse to another page. I definitely agree with Scott's recommendation that if you're thinking of using "origin" or "origin-when-cross-origin" then consider using "strict-origin" and "strict-origin-when-cross-origin" instead. I don't think I use the header for anything at all, so I'm thinking "strict-origin" might be suitable for my site - although it is tempting to jump straight to "no-referrer".
© Robert Nicholls 2002-2020
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3