Skip to content

[Website] Remove trailing slashes#9863

Merged
tobias-tengler merged 1 commit into
mainfrom
tte/fix-website-next-redirects
Jun 6, 2026
Merged

[Website] Remove trailing slashes#9863
tobias-tengler merged 1 commit into
mainfrom
tte/fix-website-next-redirects

Conversation

@tobias-tengler

Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings June 6, 2026 18:19
@tobias-tengler tobias-tengler merged commit c5b6d0d into main Jun 6, 2026
9 of 10 checks passed
@tobias-tengler tobias-tengler deleted the tte/fix-website-next-redirects branch June 6, 2026 18:19

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the website NGINX redirect configuration to enforce non-trailing-slash URLs, aligning incoming requests with the Next.js static export configuration (trailingSlash: false) to prevent trailing-slash paths from resulting in 404s.

Changes:

  • Add a global NGINX rewrite to redirect /<path>//<path> (301), leaving / untouched.
  • Document the rationale for canonicalizing trailing-slash URLs in redirects.conf.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +11 to +15
# Always strip trailing slashes. The static export uses non-slash URLs
# (`trailingSlash: false`), so any path with a trailing slash 404s. Running
# this first canonicalizes the path so every later rule and the file lookup
# operate on the slash-free form (the root `/` is left untouched).
rewrite ^/(.+)/$ /$1 permanent;
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 this pull request may close these issues.

2 participants