[BUG] Category URLs with trailing slash return 200 instead of 404 or 301

[empiricompany]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Category URLs are also accessible with a trailing slash.

For example:
https://github-openmage.loc/women.html

If I add a trailing slash:
https://github-openmage.loc/women.html/

The page should return 404 or a 301 redirect to the correct canonical URL, but instead, it returns 200.
PS: The canonical URL is always set correctly: https://github-openmage.loc/women.html

Expected Behavior

Accessing a category URL with a trailing slash must redirect with a 301 to the correct canonical URL.

Instead, the page returns a 200 OK response, even though the canonical URL is correctly set.

Steps To Reproduce

1. With this settings:

2. Manually add a trailing slash to a category url

Environment

- OpenMage: 20.14.0 
- php: 8.2

Anything else?

If I search in URL Rewrite Management, there is no URL with a trailing slash.

[Axepih]

I once looked for a solution to this problem and found this:

https://www.tech-notes.net/magento-remove-trailing-slash-from-url/

the part with the .htacces and the multi store (my case) had bothered me because I didn't want to touch it.

[empiricompany]

@Axepih Thanks! Do you think this modification can be applied to the core and is valid with any catalog URL setting?
I would keep the issue open because it's a bug that needs to be fixed.

[empiricompany]

CMS pages are also affected by this issue:
https://github-openmage.loc/customer-service
https://github-openmage.loc/customer-service/

[spinsch]

If someone implements something like this, it would be good if you can deactivate it in the backend.
For example, we use “/” as a suffix and currently have the exact opposite problem that the urls also work without “/”.

[kiatng]

Should this be fixed at the web server in .htaccess or nginx conf?

[empiricompany]

I don't think so, it should be fixed in the application.
One of my clients has a plugin from Mirasvit that solves this issue.

@spinsch If we fix the issue, a 301 permanent redirect will need to be implemented, so it won’t have any negative SEO impact and will also resolve any duplicate content that might be indexed.