[MGNLXAA-81] Activation breaks when magnolia.utf8.enabled=true; header parameters are not URL decoded anymore Created: 10/Jul/14  Updated: 14/Jul/14  Resolved: 10/Jul/14

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1.3

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLACTIVATION-88 Activation breaks when magnolia.utf8.... 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   

Upon activation the module will URLEncoder.encode(value, "UTF-8") all request parameters but doesn't decode them.
Rather than expecting all request parameters to be readily decoded by UnicodeNormalizationRequestWrapper (which was removed in MAGNOLIA-5717) we should do the decoding in the module itself.


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