[MAGNOLIA-3138] Handling permanent redirects in VirtualUriFilter Created: 16/Mar/10  Updated: 23/Jan/13  Resolved: 16/Mar/10

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

Type: Improvement Priority: Major
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-1574 Allow 301 redirects in virtualURIFilter 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   

A small addition to virtualUriFilter: for SEO you often want to remap old uris using permanent redirect (http code 301). VirtualUriFilter can now handle the redirect: prefix for uris but that leads to temporary redirects (http code 302), which are not usable in this case.

A small nice addiction would be handling a new "permanent:" prefix in virtual uri results for addressing this.



 Comments   
Comment by Fabrizio Giustina [ 16/Mar/10 ]

added for 4.3: a "permanent:" prefix (instead of "redirect:") now leads to a 301 redirect.

Comment by Magnolia International [ 16/Mar/10 ]

Cool, thanks !
Is there a reason why we construct a complete URL (scheme, server name, port) for these while we don't for regular redirects ?

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