StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POFrame breaking only cross-domain but not for iframes from the same origin?
primarykey
Id
3823875
data
AcceptedAnswerId
4186936
AnswerCount
2
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2010-09-29T16:45:05.617
FavoriteCount
0
LastActivityDate
2015-11-02T15:53:51.663
LastEditDate
2017-05-23T12:29:51.990
LastEditorUserId
-1
OwnerUserId
353267
ParentId
0
PostTypeId
1
Score
2
ViewCount
4611
LastEditorDisplayName
text
Body
<p>This question was previously <a href="https://stackoverflow.com/questions/952242/why-do-frame-breakers-work-cross-domain-and-can-you-conditionally-use-frame-brea">asked and answered</a> correctly, but there did not seem to be a solution posted.</p> <p>If a site has iframes, and one wants to prevent those from being enclosed in a frame from a different domain, simplistic frame-busting will not be useful:</p> <pre><code><script>if (top != self) top.location = location</script> </code></pre> <p>However, since cross-frame scripting to other domains should generate exceptions, something like this seems to work well inside the iframe:</p> <pre><code><script> try { if (window.document.domain != top.document.domain) { // throws exception throw "You naughty puppy!"; // Should not ever get here, right? } } catch () { top.location = "/error/naughtypuppy"; } </script> </code></pre> <p>The <code>if</code> above should be enough on its own to prevent cross-domain framing of iframes. It should only ever return <code>false</code> or throw an exception, so is there anyway the script could reach the <code>throw</code> statement in a browser?</p> <p>Would this be sufficient to prevent framing only from other domains?</p> <pre><code><script> try { var bogus = top.document.domain; } catch () { top.location = "/error/naughtypuppy"; } </script> </code></pre> <p>Edit: A similar solution is hinted at here, but one would not rely on the parent frame to include the frame-busting code. <a href="https://stackoverflow.com/questions/2365822/detect-when-iframe-is-cross-domain-then-bust-out-of-it">Detect when iframe is cross-domain, then bust out of it</a> . Essentially the same solution as "try to access the other frame and bust if an exception occurs."</p>
Tags
<javascript><iframe><same-origin-policy>
Title
Frame breaking only cross-domain but not for iframes from the same origin?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USjbindel
plurals
PostLinksPostIdRelatedPostId
1. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
2. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
3. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POFrame breaking only cross-domain but not for iframes from the same origin?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.