GitLab Pages force HTTPS
EDIT 25/05/2016: As suggested in comments, adding an option to force HTTPS would make more sense because as it appears not all are willing to force HTTP requests to HTTPS.
EDIT 09/06/2016: Github force HTTPS for
*.github.io sites since recently: https://help.github.com/articles/securing-your-github-pages-site-with-https/ and I've enabled that for one of my projects, it works great. See HTTP response for http://netwalk.github.io
This is a feature request. Currently GitLab pages can be accessed via either
https://<username>.gitlab.io with 200 HTTP code response in each.
Please enable force redirect with 301 HTTP code from http to https version. For example, if
http://<username>.gitlab.io is requested, it should result in following response:
HTTP/1.1 301 Moved Permanently Location: https://<username>.gitlab.io
Same feature is very desirable for GitLab pages with custom domains that have SSL Certificates enabled. For instance, if repo is configured with custom domain
example.com and there is SSL certificate enabled for that domain, request to
http://example.com/some-page should result in following response:
HTTP/1.1 301 Moved Permanently Location: https://example.com/some-page