Feedback for GitLab Pages without DNS wildcard - NGINX

This is a feedback issue for the NGINX implementation of GitLab Pages without DNS wildcard - MVC.

Please add your feedback or report any issues you encounter after trying out the experimental solution.

---

Disclaimer:

Based on this discussion, we are moving towards implementing 'GitLab Pages without DNS wildcard' directly into the Pages codebase. Please follow the epic and the PoC issue for future updates.

We are closing this feedback issue. If you still face any issues with the NGINX Beta version, you can add a comment in this issue and tag me ( @ngala). We will try to support if the need arises.

---

Known issues when namespace_in_path is enabled:

• Pages with Use unique domain enabled is not working without trailing "/": When namespace_in_path is enabled, Pages with U... (#438482 - closed)
• When pages_external_url has custom PORT: When namespace_in_path is enabled and pages_ext... (#438570 - closed)
  • Misbehaving without trailing "/"
  • Misbehaving auth flow
  • Other redirects
• v16.8.0 - When access_control is enabled, private pages gives 401: In v16.8.0 - namespace_in_path and access_contr... (#439679 - closed)
• v16.8.0 - User/group pages gives 401: When namespace_in_path is enabled, user/group p... (#439680 - closed)
• When the host URL is duplicated in the URL path and the URL doesn't end with a forward slash (/), the user is redirected to a malformed URL: #440465 (closed)
• When auth_redirect_uri is manually updated to non-projects url, auth flow fails: #452459 (closed)
• When listen_port is specified for GitLab Pages, redirects are misbehaving: #458587 (closed)
• When access_control is disabled, user is facing nil error: #462344 (closed)