[
https://issues.jboss.org/browse/ISPN-3153?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-3153:
----------------------------------------
Since immortal entries never die, we don't track creation time for them. We don't
wanna be doing that either cos it takes valuable space that's might only be relevant
for REST. In fact, we don't have anything that maps directly to last-modified per se.
For transient entries, we track when the entry was last used (read or write) and for
mortal entries, we track the creation time, which is not necessarily last modified time.
Last-modified returns the expected value only when timeToLiveSeconds has been set and
we're tracking creation time (mortal entry).
REST endpoint does not return Last-modified header for GET operation
if the entry was stored via HotRod or Embedded cache
-------------------------------------------------------------------------------------------------------------------------
Key: ISPN-3153
URL:
https://issues.jboss.org/browse/ISPN-3153
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 5.3.0.Beta2
Reporter: Martin Gencur
Assignee: Galder Zamarreño
Fix For: 5.3.0.Final
When an entry is stored via HotRod an embedded cache, and later retrieved via REST,the
Last-modified header looks like this:
Last Modified: null
Another observation is that when the entry is stored via REST and retrieved via REST
again, the Last-modified header is:
Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT
This is obviously wrong and this was working correctly with JDG-server which contained
ISPN 5.2. OTOH, when I set "timeToLiveSeconds" header on the request, the
Last-modified is properly set (not to 1970).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira