Issue Summary

When attempting to monitor user traffic, for health check purposes, errors that are gracefully handled by Bitbucket and thrown to clients are paired with an HTTP 200 rather than an error code matching to the message displayed. This makes using an F5, or other load balancer options, to monitor traffic for 500 class errors not possible as all errors are matched with a 200 OK indicating that the error message was successfully sent.

Environment

• Bitbucket Data Center 5.16.1
• F5 Load Balancer utilizing passive monitoring

Steps to Reproduce

• Setup a standard Data Center environment
• Encounter an error, typically caused by running out of SCM-command tickets which prompts a "Server Busy" Error page
• Review Status code of HTTP header

Expected Results

A 503 or appropriate 500 Class Status should be sent from Bitbucket to the client when displaying an error page.

Actual Results

200 OK sent.

Workaround

Utilize the /status health check endpoint to determine if the node is in an ERROR state rather than passively monitoring user traffic.