Some old fiddles broken due to HTTP/HTTPS issue
Open
Nobody has claimed this yet.
difficulty: medium
type: infra
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
See here for example: https://jsfiddle.net/69z2wepo/48909/
Mixed Content: The page at 'https://jsfiddle.net/69z2wepo/48909/' was loaded over HTTPS, but requested an insecure script 'http://reactjs.org/js/jsfiddle-integration-babel.js'. This request has been blocked; the content must be served over HTTPS.
It's as if redirect happens without preserving the protocol.
Contributor guide
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 linked JSFiddle example at https://jsfiddle.net/69z2wepo/48909/ and inspect the reported mixed-content request to reactjs.org. Trace where the HTTP URL or redirect is controlled; done means the old fiddle loads without a browser mixed-content block over HTTPS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100