301/302 redirect to remove trailing slash creates loop.

[nathan-hildebrandt]

Problem Statement

When you create a VanityURL to remove the trailing slash, it creates an infinite loop which ends in a Redirection error.

Steps to Reproduce

Here are the steps I took in the demo environment.

1. Created a VanityURL for /blog/ that 301 redirects to /blog
2. Navigated to demo.dotcms.com/blog/

redirectissue.mp4

Acceptance Criteria

Allow VanityURLs to remove trailing slash without a redirect loop occurring.

dotCMS Version

25.04.16-1

Proposed Objective

Customer Support

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.freshdesk.com/a/tickets/30535

Previous gitissue where this was resolved but looks to have come back in a recent version.
#20280

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[fmontes]

@nathan-hildebrandt This behavior is expected — dotCMS treats /blog and /blog/ as distinct URLs per RFC 3986 standards. Redirecting one to the other without server-side normalization can cause infinite loops.

I am not sure if there is a server configuration we can do to support automatic trailing slash normalization inside dotCMS, please go to the platform team or engineering team, maybe there is a environmental variable that we can use.