Subgroups named `archived` redirect users to `archived projects` instead

Summary

When a sub-group is created with the name archived, going to the sub-group's URL, redirects the you to the group's archived' page instead.

Steps to reproduce

  1. Create a group, in my case test-public1
  2. Create a sub-group named archived (in my case test-public1/archived)
  3. Going to the subgroups main page (https://gitlab.com/groups/test-public1/archived)
  4. Instead of viewing the subgroup's main page, you end up being redirected to https://gitlab.com/groups/test-public1/archived/-/archived

Example Project

I created a public test group called test-public1 and a subgroup test-public1/archived

What is the current bug behavior?

Subgroup named archived breaks something related to routing, and thinks you're trying to view that subgroup's archived page instead, and you're redirected there.

Edit I noticed that, it only happens if you go to the URL that has no trailing slash. For example this will trigger it https://gitlab.com/groups/test-public1/archived but this won't https://gitlab.com/groups/test-public1/archived/, but going to the one with the trailing slash, redirects the user to the Archived Projects page.

What is the expected correct behavior?

Going to the subgroup page, should render the subgroup's main page, and not redirect you to "Archived Projects"

Relevant logs and/or screenshots

self explanatory, I'd say.

Output of checks

This bug happens on Gitlab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

N/A

Results of GitLab application Check

Expand for output related to the GitLab application check
N/A

Possible fixes

Not familiar with Gitlab's source code.

Edited Sep 02, 2020 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading