Clarification Needed: Reproducing HTTP 500 Status with 'Undetermined' in Health Checks

[galiacheng]

Hello team,
I’m currently learning about and drafting health check guidance for Quarkus applications on Azure Container Apps, and I have a question regarding the HTTP 500 status code.
According to Specification 4.0, there are two statuses: UP and DOWN, which I can replicate in the implementation. However, Appendix A: REST Interface Specifications mentions a 500 status code with the status Undetermined. Could you kindly guide me on how to reproduce this status?

[xstefank]

Hi @galiacheng, sorry for the late response. The 500 status code is included for the unknown server errors which cannot be expected or defined by the specification. We would like the implementations to guarantee only 200 and 503 status codes, but the server can fail in different parts of the stack. So if the implementation never gets to decide which status is returned, it usually fails with 500 Internal Server Error. Please close this issue if this explanation is satisfactory.