HTTP caching
The Remote PUMA SPI REST Service 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 PUMA SPI REST Service enterprise application. This is called UserProfileRESTServlet in the WAS console. It defaults to the value 3600 seconds, that is equivalent to one hour.
How the portal implements the Remote PUMA SPI REST Service
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