-
Notifications
You must be signed in to change notification settings - Fork 48
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
Change to using Cloudflare as front-end? #68
Comments
+1 ! |
only the dns servers needs to changed? |
yes. I'd suggest setting up an account on Cloudflare first and configuring it. Then change the domain name to point to Cloudflare's name servers once that's all done. |
looks like this has now been done openlayers/openlayers#5966 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm doing this with my own Github Pages site now, and it has several advantages. The main one is that they provide a basic form of SSL, so pages stored on Github pages can be served with https (Github itself only partly supports this). This is though not properly secure, and shouldn't be used for sensitive data, but I don't think this applies to what openlayers.org is serving anyway. They recently introduced a force https option, so all http requests are automatically served as https. This should fix #53, and also openlayers/openlayers#5276. There's also an option to use http/2 (I believe this is now the default), and this should speed up for example the loading of the 'raw' examples. There are various other useful options, such as caching, all available with the free plan.
The text was updated successfully, but these errors were encountered: