[MAGNOLIA-2353] Disabling all caching in magnolia 3.6.1 Created: 04/Sep/08 Updated: 19/Jan/09 Resolved: 19/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.6.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Tyronne Mae | Assignee: | Boris Kraft |
| Resolution: | Inactive | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
How to entirely disable response caching throughout version 3.6.1, does not appear to work as it did in versions 3.5.x.. For instance we are requesting content from cms using RequestLocaleAwareI18nContentSupport so that content is returned in correct locale for client browser.. can you please advise? thanks in advance, |
| Comments |
| Comment by Jan Haderka [ 05/Sep/08 ] |
|
The most extreme way of disabling caching is to remove cache and gzip filters from filter chain (/server/filters). |
| Comment by Tyronne Mae [ 08/Sep/08 ] |
|
The disabling of the cache and gzip filters seems to have resolved this issue. We have our own caching implementation which caches magnolia http response objects per locale.. The issue manifests itself when a client browser request is made from one locale(e.g en) for a particular localized page. It appears this page still remains cached, as upon altering the locale of the client browser(e.g to de) and initiating a fresh request for the same page displays a cached response of the previous page requested.. Caching was disabled as in attached image |