
|
If you were logged in you would be able to see more operations.
|
|
|
OSCache
Created: 22/Feb/05 09:55 AM
Updated: 06/Nov/05 11:19 AM
|
|
| Component/s: |
Filters
|
| Affects Version/s: |
2.1
|
| Fix Version/s: |
2.2 RC
|
|
|
Since the 2.1 implementation of the filter remembers the time at which the data was cached, then now we may send to the client/browser/proxy some headers as to when the data will expire.
In order to do this I do the following:
CacheFilter.java: line 75:
((HttpServletResponse)response).setDateHeader(
"Expires",
respContent.getLastModified()+time*1000
);
also line 98:
((HttpServletResponse)response).setDateHeader(
"Expires",
System.currentTimeMillis()+time*1000
);
|
|
Description
|
Since the 2.1 implementation of the filter remembers the time at which the data was cached, then now we may send to the client/browser/proxy some headers as to when the data will expire.
In order to do this I do the following:
CacheFilter.java: line 75:
((HttpServletResponse)response).setDateHeader(
"Expires",
respContent.getLastModified()+time*1000
);
also line 98:
((HttpServletResponse)response).setDateHeader(
"Expires",
System.currentTimeMillis()+time*1000
);
|
Show » |
|
CACHE-83according to the Expires header. To implement this improvement, I think we need a expires value in CacheEntry.