Bug #6373
closedRudder 3.0 ncf editor chrome, clickjacking alert
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.
Updated by Florian Heigl almost 10 years ago
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...)
Updated by Dennis Cabooter almost 10 years ago
I do have the problem in Firefox. :(
Updated by François ARMAND almost 10 years ago
Dennis, did you changed some header to ?
Updated by Vincent MEMBRÉ almost 10 years ago
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 ?
Updated by Dennis Cabooter almost 10 years ago
@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
Updated by François ARMAND almost 10 years ago
- Status changed from New to Rejected
- Reproduced set to No