[MGNLCACHE-245] Take Headers and Cookies into consideration when creating cache key Created: 20/Sep/21 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Cache Modules |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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)
|
||||||||||||||||
| Epic Link: | Headless p13n Backlog | ||||||||||||||||
| Description |
|
Magnolia doesn't support caching for different headers or cookies, thus making it impossible to cache responses with different cookie or header traits. This ticket aims to improve that functionality, so that it's possible to specify for which headers (or cookies) the response should be cached. Cache should know (either via configuration or by plug-in code that resolves the headers, for example from TraitRegistry) what headers are subject of change and cache based on that information. |