-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
5.1.0.ALPHA1
-
None
-
-
Workaround Exists
-
-
Low
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
- is related to
-
ISPN-1307 REST protocol improvements for version 2
- Resolved