diff options
author | Nick Thomas <nick@gitlab.com> | 2018-03-07 17:42:09 +0300 |
---|---|---|
committer | Nick Thomas <nick@gitlab.com> | 2018-03-07 17:42:09 +0300 |
commit | 89501363417d9c0a9744a9342e292d7a2b5a589d (patch) | |
tree | 1e66a8c61e9cd97933977142ec6ec8005fc29645 /README.md | |
parent | 1ae4901c7ea49c4eec8cc26d68ad85c5c8719454 (diff) | |
parent | 00b6c5f315ac00e9da8a6de99c50b064e9f87872 (diff) |
Merge branch 'https_only' into 'master'
HTTPS-only pages
See merge request gitlab-org/gitlab-pages!50
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -45,6 +45,24 @@ current requests. a `Content-Encoding: gzip` header. This allows compressed versions of the files to be precalculated, saving CPU time and network bandwidth. +### HTTPS only domains + +Users have the option to enable "HTTPS only pages" on a per-project basis. +This option is also enabled by default for all newly-created projects. + +When the option is enabled, a project's `config.json` will contain an +`https_only` attribute. + +When the `https_only` attribute is found in the root context, any project pages +served over HTTP via the group domain (i.e. `username.gitlab.io`) will be 301 +redirected to HTTPS. + +When the attribute is found in a custom domain's configuration, any HTTP +requests to this domain will likewise be redirected. + +If the attribute's value is false, or the attribute is missing, then +the content will be served to the client over HTTP. + ### How it should be run? Ideally the GitLab Pages should run without any load balancer in front of it. |