IronLanguages / IronLanguages/ironpython.net
Try page does not work
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 22
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Currently the try page is broken due to a chain of redirects and content security policy. The following occurs, when I try to visit the page:
http://trypython.org -> 301 Moved permanently -> http://campus.codeschool.com/courses/try-python
http://campus.codeschool.com/courses/try-python -> 302 Found -> http://campus.codeschool.com/auth/codeschool
http://campus.codeschool.com/auth/codeschool -> 302 Found -> https://www.codeschool.com/oauth/authorize?[...]
https://www.codeschool.com/oauth/authorize?[...] -> 302 Found -> https://www.codeschool.com/users/sign_in
https://www.codeschool.com/users/sign_in -> 200
But the final sign in page has, not unproper for a sign-in page, the following restrictive security policy header set and just doesn't display in Chrome while leaving a Blocked by Content Security Policy in Firefox:
content-security-policy:frame-ancestors https://pluralsight.marketing.adobe.com
Extra remark: The support link in the bottom of that specific page does not link to support but rather to itself:
https://github.com/IronLanguages/ironpython.net/blob/bd602e053afefdc85b49ced0c6364ebdb75e8824/try/index.html#L46
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the redirect chain from the try page and inspect try/index.html around line 46, where the support link is mentioned. Confirm whether the failure is caused by the external redirects or the Content Security Policy, then verify that the try page loads and the support link reaches support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100