Skip to content

Project URLs use absolute URL rather than relative URL

Summary

Project URLs in the homepage (e.g. Your Work > Projects) changed to absolute URL rather than relative URL.

Steps to reproduce

  1. Spin up a 17.8.X GitLab instance.
  2. Sign in using a regular user account and create a project.
  3. Open the homepage for your account, click inspect on the project and observe that a relative path is used on href=/relative/path.

Screenshot_2025-06-04_at_3.05.23_PM

Screenshot_2025-06-04_at_3.06.59_PM

  1. Spin up a 17.11.X GitLab instance.
  2. Sign in using a regular user account and create a project.
  3. Open the homepage for your account, click inspect on the project and observe that an absolute path is used on href=https://gitlab.example.com/project/path

Screenshot_2025-06-04_at_3.42.25_PM

Screenshot_2025-06-04_at_3.42.12_PM

Example Project

What is the current bug behavior?

The homepage is using absolute path for the Project URLs.

What is the expected correct behavior?

The homepage should use relative path for the Project URLs.

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

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

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.

Edited by 🤖 GitLab Bot 🤖