[MGNLREST-314] Make sure caching of personalized content is working Created: 18/Jun/21 Updated: 13/Jul/21 Resolved: 13/Jul/21 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.8 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Jaroslav Simak |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | Headless p13n |
| Sprint: | HL & LD 32 |
| Story Points: | 2 |
| Description |
|
The Advanced Cache Module is unable to process and cache content returned from the rest endpoint because the node returned from the Delivery endpoint is not set in the AggregationState (which the Advanced Cache Module relies on). A potential solution is to set the node that is being returned from the endpoint to the aggregation state. AC:
|