What steps will reproduce the problem?
1.visit http://www.enhanceie.com/test/clickjack/, check the 8th section
with title include "A same-origin victim IFRAME, which is configured to
ALLOW-FROM a different origin only"
What is the expected result?
The iframe content is blocked
What happens instead?
the iframe content show correctly
Please provide any additional information below. Attach a screenshot if
possible.
chro...@googlecode.com
unread,
Aug 23, 2012, 11:43:18 PM8/23/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
chro...@googlecode.com
unread,
Dec 27, 2013, 10:51:14 AM12/27/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Paul, I've talked with Adam about this a few times. He'll correct me if
something has changed, but my understanding is that we're not going to add
features to XFO, but instead implement them through CSP.
https://codereview.chromium.org/91353002/ implements the 'frame-ancestors'
directive as part of CSP 1.1[1]. and I expect to land that shortly. I think
that's the right way to move forward with this feature.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
chro...@googlecode.com
unread,
Jan 23, 2014, 6:25:03 AM1/23/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
CSP 1.1: Implement the 'frame-ancestors' directive.
As defined at [1]. This patch will have no web-visible impact, as the
directive
remains trapped behind the runtime flag that's governing all CSP 1.1
hotness.
This is still behind the "Experimental Web Platform Features" flag, yes.
It'll come out to play in stable once we ship CSP 1.1, which I'm hoping
will be Real Soon Now.
chro...@googlecode.com
unread,
Jun 3, 2014, 12:05:44 PM6/3/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Getting the following in console : Refused to display 'xxxx' in a frame
because an ancestor violates the following Content Security Policy
directive: "frame-ancestors *.twitter.com".
However the content is still shown in the iframe, this is on a localhost
web server.
chro...@googlecode.com
unread,
Sep 24, 2014, 8:56:19 AM9/24/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
WONTFIXing this bug. I don't believe we should support `Allow-From` with
X-Frame-Options' broken checking behavior. 'frame-ancestors' is shipping in
both Chrome and Firefox, and is the right way to support this functionality.