Hi,

yes, makes sense to keep format - thanks, I'll create an issue for that one

Regards
Carsten

Am 07.12.2021 um 15:50 schrieb Georg Henzler:
Hi Carsten,

generally this makes sense. Currently we have the param list [1] in the html rendering, I could imagine a config option 'disableRequestConfiguration' - but I think it could be good to leave the format option open as this is just response format and not really config. WDYT?

-Georg

[1]
Supported URL parameters
tags:Comma-separated list of health checks tags to select - can also be specified via path, e.g. /system/health/tag1,tag2.json. Exclusions can be done by prepending '-' to the tag name names:Comma-separated list of health check names to select. Exclusions can be done by prepending '-' to the health check name format:Output format, html|json|jsonp|txt - an extension in the URL overrides this httpStatus:Specify HTTP result code, for example CRITICAL:503 (status 503 if result >= CRITICAL) or CRITICAL:503,HEALTH_CHECK_ERROR:500,OK:418 for more specific HTTP status combineTagsWithOr:Combine tags with OR, active by default. Set to false to combine with AND forceInstantExecution:If true, forces instant execution by executing async health checks directly, circumventing the cache (2sec by default) of the HealthCheckExecutor timeout:(msec) a timeout status is returned for any health check still running after this period. Overrides the default HealthCheckExecutor timeout
hcDebug:Include the DEBUG output of the Health Checks
callback:name of the JSONP callback function to use, defaults to processHealthCheckResults

[2] https://github.com/apache/felix-dev/blob/master/healthcheck/core/src/main/java/org/apache/felix/hc/core/impl/servlet/HealthCheckExecutorServletConfiguration.java


On 2021-12-07 15:16, Carsten Ziegeler wrote:
Hi Georg,

while we are discuss HC here :) I was thinking about adding another
osgi config to HealthCheckExecutorServlet  to allow to lock it down
and ignoring any parameters send in via http. Does that sound
reasonable to you?

Regards
Carsten


--
Carsten Ziegeler
Adobe
cziege...@apache.org

Reply via email to