How to use and provide relevant caching informations
Directions for use (REST)
Where necessary, especially for caching and concurrent access to resources, ETag (of unique version identifiers of resources) should be leveraged |
| By default, http caching must be disabled |
REST Resources
Version Control for Entities |
| Caching |
3.5.1 Standard Headers
ETag, If-Match, If-None-Match |
Standard request headers
If-Match, If-None-Match, If-Range |
Standard response headers
ETag |
| Retention policy for operation results |