Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2009-12-26 02:06:01
- johnnie
- Member
- Registered: 2007-03-10
- Posts: 58
No-cache alog with last-modified?
Hello!
Can anybody explain the rationale behind appending a no-cache to the cache-control header when a last-modified is sent out? This heavily interferes with back-end caches like apache’s mod-cache, which requires a last-modified header to properly operate, but busts out on a no-cache.
Offline
Re: No-cache alog with last-modified?
I am not sure what TXP delivers but you can set it yourself or manipulate the header pretty easy.
Try these start points:
http://blog.web-optimizer.us/2009/11/several-layers-of-caching.html
http://blog.web-optimizer.us/2009/11/client-side-caching-basics-automation.html
http://blog.web-optimizer.us/2009/11/caching-proxy-servers-and-forced-reload.html
http://blog.web-optimizer.us/2009/12/conditional-caching-several-approaches.html
Disclaimer: I am using and testing this software all the time.
Get all online mentions of Textpattern via OPML subscription: TXP Info Sources: Textpattern RSS feeds as dynamic OPML
Offline
#3 2009-12-26 11:09:40
- johnnie
- Member
- Registered: 2007-03-10
- Posts: 58
Re: No-cache alog with last-modified?
I am using apache to override the cache-control header to public (Header: cache-control set public). Whilst this may work, it does remove the max-age part of the header. Appending is not an option, since no-cache takes precedence.
Offline
#4 2009-12-31 15:26:22
- johnnie
- Member
- Registered: 2007-03-10
- Posts: 58
Re: No-cache alog with last-modified?
An additional idea would be to only include the no-cache on backend pages. This would prevent unwanted cacheing of the backend.
Offline