You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bunch of new security headers incoming, specifically COOP, COEP, CORP and CORB. We need to investigate which are appropriate to our family of sites.
Note that also Cross Origin Read Blocking (CORB) is mentioned, this depends on rules such as Access-Control-Allow-Origin: *not being used, which we currently do use (although I need to remember why we set this - there was a reason). EDIT: this was the reason.
The text was updated successfully, but these errors were encountered:
Header always set Cross-Origin-Opener-Policy "same-origin"
Header always set Cross-Origin-Resource-Policy "same-site"
Header always set Cross-Origin-Embedder-Policy "require-corp"
...but that relies on CORS being set up properly to work, and that subject is a whole other level of confusing to me, so I'll defer to someone with better knowledge - or read more about it at some point in the future.
There is a bunch of new security headers incoming, specifically COOP, COEP, CORP and CORB. We need to investigate which are appropriate to our family of sites.
Source: https://scotthelme.co.uk/coop-and-coep/
Note that also Cross Origin Read Blocking (CORB) is mentioned, this depends on rules such as
Access-Control-Allow-Origin: *
not being used, which we currently do use (although I need to remember why we set this - there was a reason). EDIT: this was the reason.The text was updated successfully, but these errors were encountered: