History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CACHE-143
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Lars Torunski
Reporter: Simone Avogadro
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
OSCache

Report expected expiry to clients/browsers/proxy

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

Issue Links:
Related
This issue relates to:
CACHE-83 CacheHttpServletResponseWrapper & Res... Major Closed
 

Flags: Patch


 Description  « Hide
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
);


 All   Comments   Change History      Sort Order:
Lars Torunski - [23/Feb/05 01:20 AM ]
Some improvements were done in CACHE-83 according to the Expires header. To implement this improvement, I think we need a expires value in CacheEntry.

Lars Torunski - [13/Mar/05 04:27 PM ]
Also add a new attribute "expire" to the jsp tag cache.