[MGNLCACHE-50] Provide possibility to exclude errors from being cached Created: 08/Oct/12  Updated: 15/Mar/21  Resolved: 15/Mar/21

Status: Closed
Project: Cache Modules
Component/s: configuration
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File DoNotStoreErrorsStore.java    
Issue Links:
Relates
relates to MAGNOLIA-3505 VirtualURI configurations that lead t... Closed
duplicate
is duplicated by MAGNOLIA-4558 Make caching of errors (and different... Closed
Template:
Patch included:
Yes
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)

 Description   

Right now, Magnolia will include/exclude items from being cached based on various rules.
One can even influence cache behaviour by setting cache headers in the response before rendering starts (and response is committed).
However there is no way to react based on some arbitrary events that happen during rendering or based on the response code. This would for example allow excluding items from cache in case someone generates number of 404 requests just by trying to fish for valid URLs on the site.

Attached is an example of executor that would not store items in case of errors, but rather then having specialized executor, this behaviour should be configurable.



 Comments   
Comment by Jan Haderka [ 15/Mar/21 ]

No demand for such feature.

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