Closed laura-rodriguez closed 8 years ago
Hi @laura-rodriguez can you give me some context on which browser you are using and whether you are using the main plunker editor, the embed, or the preview? Also, what browser are you using?
If you have a Plunk you can share to demonstrate the issue, please let me know.
Hi @ggoodman, I am using chrome (Version 51.0.2704.103 m) but it also happens to me with FF. This is the url I am using: https://plnkr.co/edit/UyInn4YpQlc5SeVUXuh6?p=preview but it also happens with a new simple project: https://plnkr.co/edit/?p=preview
Hello @laura-rodriguez, other users have reported similar issues in the past and this has been due to corporate networks injecting that header. Neither the editor, nor the run server are issuing that header:
Editor
Run server
Please consult whoever is responsible for the network environment that you run in to see if this change was recently introduced.
@ggoodman I have tried again, and it is working now. This issue not only happened to me, at my home, but also to my co-workers at the office and other friends at their home.
Hi @laura-rodriguez. I'm going to close the issue for now. If it re-appears, please open your developer console and show me exact what headers are being served both for the editor (https://plnkr.co/edit/) and for the preview (https://run.plnkr.co/
I am facing a similar issue..
Yesterday and today I was not able to run code because of next issue:Refused to display 'https://run.plnkr.co/xxxxxxx/' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.