[MAGNOLIA-3171] move CacheHeadersFilter back to core Created: 31/Mar/10 Updated: 26/Nov/13 Resolved: 26/Nov/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.3.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
talking about the filter described in to refrain:
We could rename cacheHeaders filter to HttpHeadersFilter or anything else if the "cache" name makes things confused... |
| Comments |
| Comment by Magnolia International [ 01/Apr/10 ] |
|
It IS related; the cache module decides (or can decide, or influence) what "hints" (http headers) we send back to the browser. |