HTTP caching - Remote REST service for PUMA

The remote REST service for PUMA sets the Cache-Control HTTP header in the response to public for resources that are served without authentication, and to private for URIs that require authentication.

The expiration time is defined by the max-age directive in the same header and can be configured as a number in seconds within the wp.user.restservice.maxage environment entry of the remote REST service for PUMA enterprise application. This is called UserProfileRESTServlet in the WAS admin console. It defaults to the value 3600 seconds so that is equivalent to one hour.

Parent: How the portal implements the remote PUMA REST service

Related:
URL path segment for virtual portals
Identifiers used in the Portal Implementation
Access Control Checks
Use ATOM/APP as input and output format
Switch for tunneling of HTTP methods
Context root and authentication mechanism
Lookup facility in the portal