[
https://issues.jboss.org/browse/ISPN-1425?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1425:
-----------------------------------
Git Pull Request:
https://github.com/infinispan/infinispan/pull/558 (was:
https://github.com/infinispan/infinispan/pull/558)
Workaround Description:
As indicated in the API documentation, you can get entries to be stored with configured
expiration/lifespan settings passing 0 as parameters:
https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+v...
Workaround: Workaround Exists
Incorrect settings [timeToLiveSeconds,maxIdleTimeSeconds] when
default in REST
-------------------------------------------------------------------------------
Key: ISPN-1425
URL:
https://issues.jboss.org/browse/ISPN-1425
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.1.0.ALPHA1
Reporter: Greg Autric
Assignee: Galder Zamarreño
Fix For: 5.1.0.BETA2
Attachments: Server.scala.ISPN-1425.patch, Server.scala.ISPN-1425.v2.patch
Original Estimate: 2 hours
Remaining Estimate: 2 hours
If HTTP client didn't use
timeToLiveSeconds or/and maxIdleTimeSeconds in all PUT/POST header request
Cache entry will allways use -1 for timeToLiveSeconds and -1 for maxIdleTimeSeconds
instead of current Cache settings
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira