Bug #15713
Updated by Peter Amstutz about 5 years ago
During development, I introduced an error that caused controller to return a 503 error.
However, the logging is confusing:
* nginx turns the 503 error from controller into a 500 error, so searching the controller logs for a 500 status error comes up empty
* The error message that is returned to the client is not emitted in the log.
This is similar to #15606, another situation (in keep-web) where the error message is returned to the client but missing from the log.
Proposed fix:
* Tweak nginx so it doesn't change the status code and/or return a different status code that is consistent.
* Ensure that error messages are always emitted in the request log