[jboss-jira] [JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500

[ https://issues.jboss.org/browse/WFCORE-4045?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFCORE-4045: ------------------------------------ See WFLY-10861 for the background information resulting in this. The output with this fix is: {code} $curl -v http://127.0.0.1:9990/health * Trying 127.0.0.1... * TCP_NODELAY set * Connected to 127.0.0.1 (127.0.0.1) port 9990 (#0) < HTTP/1.1 500 Internal Server Error < Connection: keep-alive < Content-Type: application/json; charset=utf-8 < Content-Length: 408 < Date: Mon, 20 Aug 2018 19:39:30 GMT < * Connection #0 to host 127.0.0.1 left intact "WFLYDMHTTP0016: Your Application Server is running. However you have not yet added any users to be able to access the HTTP management interface. To add a new user execute the add-user.sh script within the bin folder of your WildFly installation and enter the requested information. By default the realm name used by WildFly is 'ManagementRealm' and this is already selected by default by the add-user tool." {code} As discussed with [~rsvoboda] the API exposed to register http handlers from the subsystems is new and we want to keep it as simple as possible at the moment. The new ManagementHttpServer.addManagementHandler() was reusing the logic from the console to redirect to the standard error mechanism used for the console. This mechanism ends up loading the page https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (linux) or https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (windows). For this use-case, which will also be used by other subsystems which want to register a custom HttpHandler, the mechanism is to simply send a 500 status code with the text shown above. If something more advanced is needed in the future we can expand the API, but it is too early to do so without knowing the use-cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)