Skip to content
This repository was archived by the owner on Sep 30, 2020. It is now read-only.

Changed cdns for people stuck behind big firewalls #50

Merged
merged 1 commit into from
Jul 21, 2014

Conversation

imccrum
Copy link
Contributor

@imccrum imccrum commented Jul 20, 2014

No description provided.

@imccrum
Copy link
Contributor Author

imccrum commented Jul 20, 2014

@thestinger
Copy link

Using a CDN without HTTPS isn't really an option. It's important for the site to be HTTPS-only since it serves source code and binaries. It isn't right now, but putting up more barriers is going to make that take longer.

@imccrum
Copy link
Contributor Author

imccrum commented Jul 20, 2014

@thestinger I believe jsdelivr will serve content with HTTPS (the links in the pull request seem to work atleast!)

@thestinger
Copy link

Ah, I assumed it wouldn't since the main site doesn't support it.

@jimaek
Copy link

jimaek commented Jul 20, 2014

Hey guys. Yes, our website doesn't support HTTPS but the CDN does. They are on completely different infrastructures. Let me know if you have any questions.

@huonw
Copy link
Member

huonw commented Jul 20, 2014

Could we just serve all the JS ourselves?

@thestinger
Copy link

@huonw: Sure, I was only using a CDN because I didn't have much bandwidth to host this with before it was on EC2.

brson added a commit that referenced this pull request Jul 21, 2014
Changed cdns for people stuck behind big firewalls
@brson brson merged commit 03cdfda into rust-lang:gh-pages Jul 21, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants