[MGNLCACHE-125] Cache header negotiation does not work for first request after cache flush Created: 23/Oct/15 Updated: 15/Apr/16 Resolved: 02/Nov/15 |
|
| Status: | Closed |
| Project: | Cache Modules |
| Component/s: | cache core |
| Affects Version/s: | 5.3.2 |
| Fix Version/s: | 5.3.3, 5.4.3 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Frank Sommer | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 40m | ||
| 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)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Sprint: | Kromeriz 17 | ||||
| Story Points: | 3 | ||||
| Description |
|
We've got trouble with different cache headers for the same page request. Sometimes we saw the correct no-cache headers and sometimes the default cache configuration headers. The pattern is that every first request after a cache flush will use the configured browser cache policies and overwrite the cache headers set by code. See Cache header negotiation The reason seems to be that missing cache entries will be stored as uncacheable cache entries in the cache. And then the cache will bypass such cache entry requests. But for the first request the browser cache policies will overwrite the existing cache headers. |
| Comments |
| Comment by Roman Kovařík [ 02/Nov/15 ] |
|
Investigation so far:
|
| Comment by Roman Kovařík [ 02/Nov/15 ] |
|
The cause:
|
| Comment by Evzen Fochr [ 02/Nov/15 ] |
|
Commented PR. |