Bug #6373
closed
Rudder 3.0 ncf editor chrome, clickjacking alert
Added by Florian Heigl over 9 years ago.
Updated over 9 years ago.
Category:
Web - Config management
Description
Hi,
After switching to chrome I found I could not access NCF. All I got was a blank white area.
I think this isn't my setup but some protection on NCF side that blocks working with it from the rudder web UI
It might actually be an NCF issue, but filing it here, since this is where it manifests.
Noticed I now get the very same in firefox.
Can be closed, the problem was on my own side.
I put Header always set X-Frame-Options DENY in the apache config while locking it down (The rudder default config didn't even have a -SSLv3, so I went crazy...)
I do have the problem in Firefox. :(
Dennis, did you changed some header to ?
Dennis, I have other questions about that:
What is the version of python you got on your server ?
Do you have any logs in /var/log/apache2/error.log on your rudder server when accesing the editor ?
@fanf: I didn't change the header. I'm not sure if the syntax is the same in Apache 2.4 and where to put it.
@Vince_McBuche:
# dpkg -l | grep "Interactive high-level object-oriented language" | grep -v stdlib
ii python2.7 2.7.6-8 amd64 Interactive high-level object-oriented language (version 2.7)
ii python3.4 3.4.0-2ubuntu1 amd64 Interactive high-level object-oriented language (version 3.4)
# python --version
Python 2.7.6
- Status changed from New to Rejected
- Reproduced set to No
Dennis, I'm closing that one as the cause seems to be different for you, and I propose to either treat it in #6321 or open a new ticket if it appears that it is not linked with #6321.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by