[MAGNOLIA-3203] aggregation state: original uri reset after forwards Created: 18/May/10  Updated: 13/Mar/12  Resolved: 09/Dec/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.3.1
Fix Version/s: 4.5

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-3204 aggregation state loses all informati... Closed
duplicate
is duplicated by MAGNOLIA-3814 MgnlContext.getAggregationState().get... Closed
relation
is related to MAGNOLIA-3224 NPE using magnolia.utf8.enabled=true ... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Despite the fact that this uri should never change and its value should be the one shown in the browser this value is updated after a forward.

The value gets updated in the ContentTypeFilter: reset aggregation state, set new value

This is a bug, or at least does not match the concept but this behavior exists since 3.5 and changing it now could have side effects.


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