-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR] system_update_1063()
doesn't account for existing x_frame_options
variable from D7
#4080
Comments
system_update_1063()
doesn't account for existing variable from D7system_update_1063()
doesn't account for existing x_frame_options
variable from D7
I have filed a PR that:
PS: can someone with the right access permissions close backdrop/backdrop#1426 ? |
system_update_1063()
doesn't account for existing x_frame_options
variable from D7system_update_1063()
doesn't account for existing x_frame_options
variable from D7
...the change record in https://api.backdropcms.org/change-records/backdrop-core-now-protected-against-clickjacking-default-x-frame-options-sameorigin should be updated to indicate support for configuring |
This branch has conflicts that must be resolved. I wonder if this issue is still relevant after #2805? |
This is with re to a change that was implemented in Backdrop 1.9.0, directly via this PR, as part of #2013 (change record).
According to the respective D7 change record, this could have been set with the
x_frame_options
in settings.php:We have added
"x_frame_options": "SAMEORIGIN"
in our defaultsystem.core.json
file, so new sites will be set to this, and also in our respective update hook, we are doing this:Never are we reading from any existing variable set earlier (so D7 to Backdrop upgrades will miss to detect if this was set to something different), nor are we allowing people to override this in their
settings.php
.PR by @klonos: backdrop/backdrop#2895
The text was updated successfully, but these errors were encountered: