[MSITEMESH-43] Invalid security token if fragment is requested from another public instance Created: 15/Aug/16  Updated: 16/Dec/16  Resolved: 16/Dec/16

Status: Closed
Project: SiteMesh
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLCACHE-145 Provide a local scoped component whic... Closed
supersession
is superseded by MSITEMESH-13 Don't create a new connection for fra... 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
Sprint: Kromeriz 61
Story Points: 1

 Description   

There is a security token registry singleton for each instance...there could be a request for fragment from one public to an another...then it fails with

Request for 'http://...' has fragment header with invalid security token...

Workaround: set baseUrl to localhost https://documentation.magnolia-cms.com/display/DOCS/SiteMesh+module#SiteMeshmodule-Tagrulebundles

-Suggested solution: drop security token registry in favour of MGNLCACHE-145.-
Update: The issue is obsolete since MSITEMESH-13.


Generated at Mon Feb 12 10:57:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.