anchor.diff:  ----
   
   [[webflux-headers-cache-control]]
  -==== Cache Control
  +== Cache Control
   In the past Spring Security required you to provide your own cache control for your web application.
   This seemed reasonable at the time, but browser caches have evolved to include caches for secure connections as well.
   This means that a user may view an authenticated page, log out, and then a malicious user can use the browser history to view the cached page.
  
positive.code: 
  
  [[webflux-headers-feature]]
  ==== Feature Policy
  
  https://wicg.github.io/feature-policy/[Feature Policy] is a mechanism that allows web developers to selectively enable, disable, and modify the behavior of certain APIs and web features in the browser.
  
  
negative.code: https://www.w3.org/TR/CSP2/[W3C Candidate Recommendation]
  
  [[webflux-headers-referrer]]
  == Referrer Policy
  
  https://www.w3.org/TR/referrer-policy[Referrer Policy] is a mechanism that web applications can leverage to manage the referrer field, which contains the last page the user was on.
  
  