More control over cache headers on simple actuator web endpoints

I exposed some resources (non functional) as endpoints in the actuator, the clients use the cache headers to know how much time they are going to keep that resource cached and avoid repeated calls.

I would like to use a @WebEndpoint instead of @RestEndpointController with just a configuration or an annotation.

Could time-to-live affect response headers? could you offer a new configuration just for that?

Start by reading the actuator entry points named in the issue, @WebEndpoint and @RestEndpointController, and trace how time-to-live is currently handled. Compare the proposed configuration or annotation approaches, then verify that the selected behavior produces the intended cache headers for non-functional web endpoint resources.