[MAGNOLIA-1047] VirtualURI Filter does not handle redirects and forwards correctly Created: 13/Sep/06  Updated: 23/Jan/13  Resolved: 13/Sep/06

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0 RC2
Fix Version/s: 3.0 RC4

Type: Bug Priority: Major
Reporter: Sameer Charles Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

currently there is no way to assign a virtual URI to a page without skipping all filters, and if you use "redirect:" it does a server
side redirect which jeopardises any search engine index calls.

We should have a clean mapping in virtual URI, something like

redirect:/some_uri (server side redirect)
forward:/some_uri (request dispatcher forward while discarding the rest of the filter chain)
/some_uri (simply modifying path and resetting the filter chain to start again)



 Comments   
Comment by Sameer Charles [ 13/Sep/06 ]

implemented

how to use:

  • for server side redirects
    add redirect: before the path to which fromURI should be redirected (eg. redirect:/www.google.com)
  • for jsp / servlets where request needs to be simply forwarded
    add forward: before the resource path (eg. forward:/thumbnail.jsp)
  • for all other virtual URI's, pages, resources etc..
    simply give a path (eg. /index.html)
Generated at Mon Feb 12 03:23:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.