Listen via http and https for GitLab Pages on a single GitLab instance
Summary
Ability to listen via http
and https
for GitLab Pages on a single GitLab instance.
Currently it is not possible via configuration settings in gitlab.rb
With gitlab.rb
as
external_url 'https://gitlab.ohl3pohl9n-gitlab.astrachan-gitlab.net'
nginx['redirect_http_to_https'] = true
## Pages
pages_external_url 'https://pages.ohl3pohl9n-gitlab.astrachan-gitlab.net'
pages_nginx['redirect_http_to_https'] = false
## Letsencrypt
letsencrypt['enable'] = false
we get
~# grep -Ei listen /var/opt/gitlab/nginx/conf/*
/var/opt/gitlab/nginx/conf/gitlab-http.conf: listen *:80;
/var/opt/gitlab/nginx/conf/gitlab-http.conf: listen *:443 ssl http2;
/var/opt/gitlab/nginx/conf/gitlab-pages.conf: listen *:443 ssl http2;
showing that we do not listen on Port 80.
This is possible using GitLab Pages via SAAS
e.g.
we can access
- https://gitlab-gold.gitlab.io/astrachan-tests/public/project-plain-pages/ # https
- http://gitlab-gold.gitlab.io/astrachan-tests/public/project-plain-pages/ # http
Proposal
Allow flexibility to use http but still have https as an optional access route.
References
ZD Customer request - internal link only