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
{{ message }}
Repository navigation
Set default frame-ancestors on default Content-Security-Policy #532
We should consider setting a default frame-ancestors directive for the Content Security Policy. The frame-ancestors directive is the new iteration of the X-Frame-Options header, and as such setting a directive in both spots might be prudent.
Since our default XFO policy is sameorigin, if we decide to take upon this task, we should set the default frame-ancestors value to be self.
Some counterpoints: setting both the X-Frame-Options and the frame-ancestors directive will cause the XFO header to be overriden by the frame-ancestors directive. This means that if a user is trying to change some framing functionality, and only changes the XFO header, they might be confused as to why the functionality didn't actually change.
This means that if a user is trying to change some framing functionality, and only changes the XFO header, they might be confused as to why the functionality didn't actually change.
The override approach/mechanism wouldn't change, right? Just that they need to override both, correct?
Also, FWIW, I am for the :whynotboth: approach and the lack of a frame-ancestors default bothered me slightly.
Activity
misfir3 commentedon Oct 21, 2024
The override approach/mechanism wouldn't change, right? Just that they need to override both, correct?
Also, FWIW, I am for the
:whynotboth:approach and the lack of aframe-ancestorsdefault bothered me slightly.