You need to sign in or sign up before continuing.
Pages Access Control Redirects to HTTP
Our GitLab instance operates with a blocked port 80. With access control enabled, the authentication workflow downgrades from https to http. Because port 80 is blocked, this results in timeouts when connecting to pages with access control enabled.
Expected behavior: If a user accesses gitlab pages over https they should not be downgraded to http for the authentication workflow.
Example authentication workflow:
https://test.example.io/example-project ->
Note the change from https to http
v
https://projects.example.io/auth?domain=http://test.example.io/example-project&state=***== ->
https://example.com/oauth/authorize?client_id=****&redirect_uri=https://projects.example.io/auth&response_type=code&state=****== ->
https://projects.example.io/auth?code=***&state=*** ->
Accessing GitLab over http results in timeout
v
http://test.example.io/auth?code=***&state=***
This behavior can be reproduced by using a browser developer console in network view to see the redirect chain and the transition from https to http.
Here is our pages configuration:
pages_external_url "https://example.io"
gitlab_pages['enable'] = true
pages_nginx['ssl_certificate'] = "/etc/ssl/certs/example.cer"
pages_nginx['ssl_certificate_key'] = "/etc/ssl/private/example.key"
gitlab_pages['access_control'] = true