.NET Components for Externalized Configuration, Database Connectors, Service Discovery, Logging and Distributed Tracing, Application Management, Security, and more.
During recent trace actuator work, we discovered that the Content-Type header in actuator responses is not being handled correctly. It might make sense for individual actuator endpoints to be able to specify their media type (eg: /httpExchanges should only ever return v3) and not exclusively respond to an Accepts header and falling back to v2 if the header wasn't found.
We should investigate if any actuator front-ends we care about even pay attention to this header, and if so, how Spring determines the media type to use in the response.
During recent trace actuator work, we discovered that the Content-Type header in actuator responses is not being handled correctly. It might make sense for individual actuator endpoints to be able to specify their media type (eg: /httpExchanges should only ever return v3) and not exclusively respond to an
Accepts
header and falling back to v2 if the header wasn't found.We should investigate if any actuator front-ends we care about even pay attention to this header, and if so, how Spring determines the media type to use in the response.