Skip to content

Bug with hostnameOverride when moving a project

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Using hostnameOverride to overwrite domain causes redirect to use incorrect URL.

global:
  hosts:
    domain: code.example.com
    gitlab:
      name: code.example.com
      hostnameOverride: code.internal.net

If a team is transferring/moving a project inside GitLab to a new path. GitLab returns the internal URL instead of the external URL in the redirect URL.

GET https://code.example.com/api/v4/projects/test-v2.0%2Ftest%2Ftest-for-ticket%2Fmy-awesome-project -v
...
< Location: https://code.internal.net/api/v4/projects/1
...

Steps to reproduce

Create a GitLab instance with the configuration mentioned above with WAF and move a project.

What is the current bug behaviour?

The redirect is pointing to the incorrect URL.

What is the expected correct behaviour?

That the redirect is pointing to the correct URL.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Related ticket: https://gitlab.zendesk.com/agent/tickets/633757 (internal only)

Edited by 🤖 GitLab Bot 🤖