[MAGNOLIA-2442] CacheControl: no-cache is ignored by magnolia cache. Created: 21/Oct/08  Updated: 23/Jan/13  Resolved: 22/Jan/09

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.6.3
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MAGNOLIA-3158 cache: make server side re-caching of... Closed
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   

At the moment cache ignores any incoming requests for non cached content from client and serves them from cache anyway. Default caching policy should take value of Cache-Control field in account when deciding what to do about request.



 Comments   
Comment by Jan Haderka [ 21/Oct/08 ]

committed on 3.6 branch as r19239 and on trunk as 19238.

Comment by Magnolia International [ 22/Oct/08 ]

I'm not convinced we should allow this by default, as it might put unnecessary load on the servers ... ?
(even though I see the need for an easy way to enforce getting fresh content, of course...)

Comment by Jan Haderka [ 22/Jan/09 ]

This is a "standard" way to tell servers not to use cached content. If someone wants to make DOS attack it will not stop them.

Generated at Mon Feb 12 03:36:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.