websites do not load. Get error message "Blocked by X-Frame-Options Policy"
My websites which used to load in the past no longer load. Examples: www.buffynjohn.com, www.writeabookforfun.com, www.vernonadvocate.com. Get error message "Blocked by X-Frame-Options Policy"
All Replies (5)
hi, you will have to raise this issue with your hosting provider angelfire/lycos, since apparently they don't allow their content in frames on a different domain anymore.
A possible workaround is to use the right-click context menu on the page:
- This Frame -> "Show Only This frame" or "Open Frame in New Tab"
Okulungisiwe
The suggested solutions did not work in solving my problem "My websites which used to load in the past no longer load but result in the following error message "Blocked by X-Frame-Options Policy"
The web pages that will not load are identified in the original request for support. These addresses are domain names purchased from GoDaddy and are forwarded from the original Angelfire addresses are identified in the attached image.
(See image)
It would appear the problem is not with the ability to load addresses from Angelfire but may be caused by a problem with the forwarding of the address to the GoDaddy new address.
Do you have an answer as to why the GoDaddy purchased domain does not load and the angelfire original address representing the same page does load.
I look forward to a quick solution to this problem since the web GoDaddy addresses represent active business web pages.
Thanks for your continued effort.
Dr. John T. Whiting'
hi, it's less an issue with forwarding, but rather the sites on your godaddy domains are embedding the content of your angelfire.com sites in an iframe.
however the angelfire.com server sends the HTTP header X-Frame-Options: SAMEORIGIN which is basically an instruction to webbrowsers that its content is not allowed to be embedded on 3rd-party domains:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
The www.angelfire.com server sends the "X-Frame-Options: SAMEORIGIN" header via the HTTP response headers and this makes it impossible for browser like Firefox that obey this feature to load these pages in an iframe.
If this worked before then this is a recent change on the server.
Only if you directly open the page in a tab like I posted above as a workaround then you be able to open the page.
You would have to use a location redirect to the angelfire.com website instead of opening the page in an iframe.