Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,408
Community Members
 
Community Events
176
Community Groups

Fishsye CrossDomain Problem?

Hi ,

I am using asp.net for for my website and i am using fisheye as a tool in my website.

Now When I Redirect fisheye request it gives me cross platform issues.

 

<iframe id="fisheyFrame" src="fisheyeURL" name="fisheyFrame" allowtransparency="true" frameborder="0" style="width:100%;height:500px"></iframe>

Error Fire when run page :

Uncaught SecurityError: Blocked a frame with origin "http://localhost:8060" from accessing a frame with origin "http://localhost:5449". Protocols, domains, and ports must match.

How can i solve it ???

Thanks,

1 answer

0 votes

Hi,

This is caused by Same Origin security policy, there is a lot of materials on this matter on the web, e.g. http://stackoverflow.com/questions/25098021/securityerror-blocked-a-frame-with-origin-from-accessing-a-cross-origin-framehttp://stackoverflow.com/questions/25893006/uncaught-securityerror-blocked-a-frame-with-origin-null-from-accessing-a-fram or http://en.wikipedia.org/wiki/Same-origin_policy

Interesting is also the URL you are using, http://localhost:8060/.  Remember this might work well on your local machine where FishEye instance is running on the same box, but external users would not be able to access FishEye via this URL.  Use full qualified domain name of the box hosting FishEye preferrably.

Finally, by the same origin policy error you mentioned, I'm guessing you are trying to interact with FishEye displayed in the iframe by JavaScript, aren't you?  Let me know what kind of integration are you trying to achieve, perhaps there are better ways of providing such integration?   You may want to consume FishEye REST APIs for instance to interact with FishEye application, that might be easier approach to overcome the same origin policy limitations.

Kind regards,
Piotr 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events