Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Not having a trailing slash redirects to landing page #179

Open
zaaakher opened this issue Feb 12, 2025 · 0 comments · May be fixed by #180
Open

Bug: Not having a trailing slash redirects to landing page #179

zaaakher opened this issue Feb 12, 2025 · 0 comments · May be fixed by #180

Comments

@zaaakher
Copy link
Contributor

Describe the bug
Visiting any first-level page in the docs redirects to the landing page if no trailing slash is added at the end.

To Reproduce
Steps to reproduce the behavior:

  1. Visit https://coolify.io/docs/databases (or type it manually in the address bar)
  2. You'll see that it redirects you to the landing page while keeping the subpath but removing "/docs" (https://coolify.io/databases)
  3. Now try visiting https://coolify.io/docs/databases/
  4. It works fine now.

Expected behavior
I think the trailing slash shouldn't make a difference when visiting those pages. I noticed that there are links to the docs in my Coolify instance that keep taking me to the landing page. I was gonna make a PR in Coolify to fix these links but I think it should fixed here instead.

Desktop (please complete the following information):

  • OS: MacOS Sequoia 15.3
  • Browser Chrome
  • Version 133.0.69453.54

Additional context
I first noticed this only happens with the "overview" pages of each section. but just as I'm documenting this issue I noticed the other pages also have a problem with the trailing slash. Try visiting https://coolify.io/docs/databases/mysql and then in the url address add a trailing slash at the end of the address and you'll see different content (or no content at all) but still remain in the docs website

@zaaakher zaaakher linked a pull request Feb 12, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant