anchor.diff:  NOTE: The prefix `management.endpoint.<name>` is used to uniquely identify the
   endpoint that is being configured.
   
  -
  -
  -[[production-ready-endpoint-hypermedia]]
  +NOTE: When making an authenticated HTTP request, the `Principal` is considered as input to
  +the endpoint and, therefore, the response will not be cached.
  +
  +
  +
  +[[production-ready-endpoints-hypermedia]]
   === Hypermedia for Actuator Web Endpoints
   A "`discovery page`" is added with links to all the endpoints. The "`discovery page`" is
   available on `/actuator` by default.
  
positive.code: 
  
  
  [[production-ready-endpoint-cors]]
  === CORS Support
  https://en.wikipedia.org/wiki/Cross-origin_resource_sharing[Cross-origin resource sharing]
  (CORS) is a https://www.w3.org/TR/cors/[W3C specification] that lets you specify in a
  
negative.code: 
  
  
  [[production-ready-endpoints-custom-mapping]]
  === Actuator Web Endpoint Paths
  By default, endpoints are exposed over HTTP under the `/actuator` path by using the ID of
  the endpoint. For example, the `beans` endpoint is exposed under `/actuator/beans`. If you
  want to map endpoints to a different path, you can use the
  `management.endpoints.web.path-mapping` property. Also, if you want change the base path,
  you can use `management.endpoints.web.base-path`.
  
  The following example remaps `/actuator/health` to `/healthcheck`:
  