Feature #484
Allow override of default Cache-Control & Expires HTTP header
Start date:
04/03/2012
Due date:
% Done:
0%
Estimated time:
Browser (if web client):
Description
I feel the default provided Cache-Control & Expires HTTP headers of
Cache-Control: max-age=0, must-revalidate, proxy-revalidate Expires: 0
work fine in most use cases, however if a programer wants to adjust them, they cannot.
If we attempt to do the following...
ResponseObject.addHeader('Cache-Control', "max-age=86400, public, no-cache, must-revalidate");
The HTTP header will come back with our string concatenated to the end of the default (which I'm unsure if this is a valid header anymore).
Cache-Control: max-age=0, must-revalidate, proxy-revalidate, max-age=86400, public, no-cache, must-revalidate
So I would propose that if the programer tries to set a HTTP header that already has a default defined in the plugin that you simply overwrite the default value with the programer defined one.
History
Updated by Patrick Talbot about 12 years ago
- Status changed from New to Closed
You are right. Next version will allow users to set these headers explicitely.
If not set, the defaults will be used.