-
Bug
-
Resolution: Workaround exists
-
Major
-
None
-
1.7.6
-
None
-
None
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).
Acceptance criteria
- caused by
-
MGNLADVCACHE-83 Paths created for dynamic fragments are not site aware
- Closed