[MGNLADVCACHE-67] Dynamic are with state.originalBrowserURL Created: 03/Feb/16  Updated: 11/Jul/19

Status: Open
Project: Advanced Cache
Component/s: None
Affects Version/s: 1.7.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Booxware Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Date of First Response:

 Description   

When magnolia component is placed inside area which is configured to be dynamically refreshed and the component ftl uses: state.originalBrowserURL the value returned by originalBrowserURL is not the browserURL pointing to a page but URL pointing to the component directly.



 Comments   
Comment by Roman Kovařík [ 03/Feb/16 ]

Hello,
since dynamic components are requested as separate requests, originalBrowserURLs are indeed the urls to the components. Any problem to handle this directly in the FTL?

Regards
Roman

Comment by Booxware [ 03/Feb/16 ]

OK the easy walk-around solution could be to use freemarker string utils to get rid of everything what is after ~ character and eventually have the url equal to the one before introducing dynamic cache. Is this the solution you would recommend?

Comment by Roman Kovařík [ 03/Feb/16 ]

Stripping everything after ~ would work for dynamic areas (http://page~area1~). If the problem occurs also for dynamic components (http://page/component), you would need to introduce more clever logic to strip the component part.

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