Question
Blocking iframe because it set 'X-Frame-Options' to 'DENY'.
- Posted March 25, 2017
- NginxPHPUbuntu 16.04
I uploaded a project on the php server in my droplet which has both node and php server block on nginx. But when i opened it in the browser it isnt working because it works with i frames and in the console i see
Refused to display ‘myiframe’ in a frame because it set ‘X-Frame-Options’ to ‘DENY’.
And also Uncaught SecurityError: Failed to read the ‘contentDocument’ property from ‘HTMLIFrameElement’: Sandbox access violation: Blocked a frame at “https://www.mydomain.com” from accessing a frame at “null”. The frame being accessed is sandboxed and lacks the “allow-same-origin” flag.
What’s the most secure way to deal with those headers on nginx and php?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
@tamburrinipietro89 Change it from
DENYtoSAMEORIGIN. That keeps a lot of the security, while it should make your app work. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options@tamburrinipietro89 Change it from
DENYtoSAMEORIGIN. That keeps a lot of the security, while it should make your app work. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-OptionsI followed the same and changed in the ssl-params.conf but nothing seems to be changed.
I got this error on my Moodle site after installing the self-signed SSL certificate on my ubuntu 18.04 and 16.04 with apache2 web server installed on it. First, go to this location on your ubuntu server
/etc/apache2/conf-availableand open the filessl-params.conf, which you must have created for installing an SSL certificate. Make this Change in the file from DENY to SMAEORIGINHeader always set X-Frame-Options SAMEORIGINThis worked for me.