[MGNLADVCACHE-89] FragmentInjectionLister can produce invalid content path Created: 07/Apr/17  Updated: 30/Jul/18  Resolved: 30/Jul/18

Status: Closed
Project: Advanced Cache
Component/s: None
Affects Version/s: 1.7.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Zdenek Skodik 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:
Relates
causality
caused by MGNLADVCACHE-83 Paths created for dynamic fragments a... 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
Story Points: 2

 Description   

At environment like this:

Due to running two publish server we cannot use the public domain for this (since you might end up on the wrong publish server with the request), so we are using the webserver in front of each publish server as the baseUrl.

So that getting the value from the webserver doesn't work as whole workspace path is excepted for the content to be resolved. It's especially an issue for multisite/domain setups.

Shouldn't be an issue for Magnolia 5.5 branch due to refactored baseUrl resolving (to be double checked).


Generated at Sun Feb 11 23:10:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.