-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Custom URL Rewrite where the request path ends with a forward slash is not matched #8264
Labels
bug report
Component: CatalogUrlRewrite
Fixed in 2.1.x
The issue has been fixed in 2.1 release line
Fixed in 2.2.x
The issue has been fixed in 2.2 release line
Issue: Format is valid
Gate 1 Passed. Automatic verification of issue format passed
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Comments
hostep
added a commit
to hostep/magento2
that referenced
this issue
Jan 28, 2017
…th has a trailing forward slash. Fixes magento#8264.
Hi @hostep , thanks for report. |
miakusha
added
the
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
label
Feb 8, 2017
In order to make the complete fix next cases should be supported:
|
This was referenced Jul 1, 2017
magento-team
added
2.1.x
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
bug report
Component: CatalogUrlRewrite
labels
Jul 31, 2017
Internal ticket to track issue progress: MAGETWO-70255 |
Internal ticket to track issue progress: MAGETWO-70505 |
magento-engcom-team
added
2.1.x
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
bug report
Component: CatalogUrlRewrite
and removed
G1 Passed
labels
Sep 5, 2017
magento-engcom-team
added
2.1.x
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
bug report
Issue: Format is valid
Gate 1 Passed. Automatic verification of issue format passed
Component: CatalogUrlRewrite
labels
Sep 11, 2017
Fixed in 2.2.0 and 2.1 releases. @hostep thank you for report |
magento-engcom-team
added
Fixed in 2.1.x
The issue has been fixed in 2.1 release line
Fixed in 2.2.x
The issue has been fixed in 2.2 release line
labels
Sep 20, 2017
magento-devops-reposync-svc
pushed a commit
that referenced
this issue
Jun 9, 2023
ACQE-4889: Bengals mainline deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug report
Component: CatalogUrlRewrite
Fixed in 2.1.x
The issue has been fixed in 2.1 release line
Fixed in 2.2.x
The issue has been fixed in 2.2 release line
Issue: Format is valid
Gate 1 Passed. Automatic verification of issue format passed
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Preconditions
Steps to reproduce
Expected result
In the frontend, going to
http://mydomain/test/
redirects you tohttp://mydomain/contact/
Actual result
In the frontend, going to
http://mydomain/test/
gives you a404 Not Found
Solution
Change the
trim
toltrim
in Magento\UrlRewrite\Controller\Router::getRewrite, otherwise the trailing slash will be removed and the url will never match.(You need to flush your cache after changing this for some reason.)
Discussion
We want to import a bunch of custom redirects since we want to migrate an old custom build shop to magento 2 and we want to redirect using 301 headers from their old url structure to the new structure. The old structure uses a lot of url's with trailing slashes and this bug prevents it from redirecting properly to the new url structure. If we don't fix it, we would lose a bunch of Link Juice (SEO term) from the old url structure and that would very be bad.
Credits
Thanks to @LoganGS who discovered this bug and the solution over here: #6700
The text was updated successfully, but these errors were encountered: