jsfiddle mixed content warning

[jfirebaugh]

The page at 'https://www.mapbox.com/mapbox.js/example/v1.0.0/' was loaded over HTTPS, but is submitting data to an insecure location at 'http://jsfiddle.net/api/post/library/pure/': this content should also be submitted over HTTPS.

[jfirebaugh]

Doesn't look like jsFiddle provides a https API. 😦 @tmcw Do you think this feature is worth having mixed content warnings on all our example pages?

[tmcw]

Do you think this feature is worth having mixed content warnings on all our example pages?

Yes, but feel free to confirm w/ segment.io tracking

[lyzidiamond]

Bumping this. Is it worth it? Is there another API we can switch to that does HTTPS? It doesn't look like jsbin does, but maybe there are others?

[jfirebaugh]

It looks like jsfiddle.net might support https now.

[JamesSCV]

Looks like something broke, yet again. jsfiddle.net is being served over https. but when I add jquery ui as a framework extension i get the mixed content warning and it blocks jquery ui. I think the issue is in chrome.

[tmcw]

Are you adding jquery ui with an https url?

[JamesSCV]

I'm using jsfiddle's built in jquery ui. For example, I create a new jsfiddle, select 'jQuery 1.7.2' from the dropdown on the left, then check 'jQuery UI 1.8.18'. When I click run, chrome throws the following error in console. "Mixed Content: The page at 'https://fiddle.jshell.net/_display/' was loaded over HTTPS, but requested an insecure script 'http://code.jquery.com/ui/1.8.18/jquery-ui.min.js'. This request has been blocked; the content must be served over HTTPS"

I'm not sure this issue has anything to do with mapbox.js now that I look into it further. Seems to be an issue on jsfiddle.net's end.