On one of my two FishEye instances the main content pane in the admin area is not loading, the area just stays empty.
image2016-10-18 8:9:6.png
Chrome shows the following error in the console:
Multiple 'X-Frame-Options' headers with conflicting values ('DENY, SAMEORIGIN') encountered when loading 'https://example.com/fisheye/static/oe7e6y/gwt/AdminGwtModule/3B142E9B95B0FCA6FE215BE8F6761A6D.cache.html'. Falling back to 'DENY'.
What can I change to send the correct frame options header?
This happened first with FishEye 4.1.0, but upgrading the server to 4.2.0 didn't solve the issue.
Parts of FishEye & Crucible application depends on IFrame usages. Most probably you have some server proxy which adds X-Frame-Options header. FishEye & Crucible on it's own doesn't add those headers.
You should remove the header completely or change it to SAMEORIGIN value.
Thanks for the hint with the proxy, the apache in front of it actually had a
Header always set X-Frame-Options DENY
directive set in conf.d/security. Now I'm just wondering why this behaviour didn't appear before and started suddenly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hard to tell, either you didn't open any page which uses IFrame or you just simply accessed application directly without proxy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My freind bought a work truck it has rerverse camera and wires an mounts no monitor need specific on monitors
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.