Security warnings on GitLab Pages sites while unique domain is enabled
Summary
When unique domain is enabled, Chrome is showing security warnings on GitLab Pages sites. Chrome is flagging them as "Dangerous" with the message in the screenshot.
Steps to reproduce
Example Project
What is the current bug behavior?
When unique domain is enabled, some pages sites are flagged "Dangerous" by Chrome browser.
What is the expected correct behavior?
Pages site should not be flagged as "Dangerous".
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing)
Possible fixes
Users can disable unique domains for their Pages site, but this action will reintroduce an issue that is resolved by unique domains: &9347 (closed)