Click here to Skip to main content
15,886,802 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
Hi All,

We are getting clickjecking vulnerability and it suggest to use x-frame option in response header.

What I have tried:

we have added x-frame option DENY is response header. So it should not allows to iframe application.

Now using developer tool i can see response contains with x-frame option DENY. But still I am able to open application in iframe.

Can anyone pleaser suggest.

Thanks.
Posted
Updated 7-Dec-20 23:47pm
v2

1 solution

X-Frame-Options - HTTP | MDN[^]

If you can still load your page in an <iframe>, then either you haven't set the header properly, or you are using a really old browser which doesn't support the header - eg: Internet Explorer 7.

NB: In more recent browsers, the X-Frame-Options header is essentially obsolete. It can be replaced with the frame-ancestors directive of your content security policy.

Content-Security-Policy - HTTP | MDN[^]
CSP Cheat Sheet[^]
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900