[MAGNOLIA-2589] Remap different possible url to the same while accessing the page Created: 27/Jan/09  Updated: 19/Dec/16  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.0
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1529 URLs with trailing slash result in br... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Currently one page can be accessed in multiple different ways, i.e.:

For SEO it would be better if first two cases are re-mapped to the third.
The second case can be mapped using VirtualURIMapping

class=i.m.cms.beans.config.RegexpVirtualURIMapping
fromURI=/(.*)/$
toURI=redirect:/#1.html

Solving the first case using VirtualURIMapping would require mapper intelligent enough to parse the url, figure out if there are any query params. Something along lines of

class=i.m.cms.beans.config.RegexpVirtualURIMapping
fromURI=/(.*[^'.html'])(\\?)(.*)
toURI=redirect:/$1.html$2$3

and for requests without any query params:

class=i.m.cms.beans.config.RegexpVirtualURIMapping
fromURI=/([^\\?]*)$
toURI=redirect:/$1.html

Or possibly combination of the two patterns above into one covering both cases - w/ and w/o query params.
However since default extension can be configured in admin interface, this mapping should be smart enough to use the default extension rather then blindly mapping everything to html.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:38:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.