-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leaderboard <iframe> widget "refuse to connect" #3305
Comments
Good catch. This seems to be a bug that appeared with the Python3 version of CodaLab. It may be linked this other access denied: We need to make some testing on our side. @dtuantran any thoughts on this? |
Hi @Didayolo, I am one of the other organizers for this competition. Thank you and @dtuantran very much for looking into this! Please let us know if there's any more info we can provide to help fix this bug. |
Hi @Didayolo @dtuantran , just want to follow up on this post to see if there's any solutions. Thanks! |
It seems the |
@DeepDuke Thank you for reporting that the problem persists. Unfortunately, right now, nobody is working on this problem. As CodaLab is an open-source community project, you are kindly invited to contribute if you think that you can find the source of the problem. |
I am trying to embed our CodaLab competition leaderboard into another website. I am using CodaLab's generated iframe, but I get the message on the webpage "codalab.lisn.upsaclay.fr refused to connect." (see attached image).
Specifically, here is CodaLab's generated leaderboard widget iframe code that is not working:
<iframe src="http://codalab.lisn.upsaclay.fr/competitions/leaderboard_widget/9304/" style="height: 500px; width: 100%; border: none;"></iframe>
I tried it with Chrome, Edge, and Firefox browsers. All do not work.
From what I can find online, it seems that the issue is the website desired to be in the iframe (i.e. CodaLab) has a Content Security Policy set to disallow their webpages from being included in iframes. Thus, the website (in this case CodaLab) would need to change their policy.
Can you confirm that this is the issue? If not, do you know any fixes? I appreciate your help!
Edit: Updating with new image of error message describing the root cause of the issue. Looking at this StackOverflow discussion, it seems that CodaLab would need to edit their IIS config file. Can this be done?
The text was updated successfully, but these errors were encountered: