[ https://issues.apache.org/jira/browse/MESOS-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511270#comment-15511270 ]
Benjamin Mahler commented on MESOS-6220: ---------------------------------------- Added as an API change in the CHANGELOG: {noformat} commit a640eb25a9ebc4b2409c86df5cc71bd625427001 Author: Benjamin Mahler <bmah...@apache.org> Date: Wed Sep 21 14:36:49 2016 -0700 Added MESOS-6220 as an API change to the 1.1.0 CHANGELOG. {noformat} > HTTP handler failures should result in 500 response rather than 503 response. > ----------------------------------------------------------------------------- > > Key: MESOS-6220 > URL: https://issues.apache.org/jira/browse/MESOS-6220 > Project: Mesos > Issue Type: Improvement > Components: libprocess > Reporter: Benjamin Mahler > Assignee: Benjamin Mahler > Priority: Minor > Fix For: 1.1.0 > > > Currently, when an HTTP handler fails, libprocess will send a {{503 Service > Unavailable}} (see > [here|https://github.com/apache/mesos/blob/8322b403cbaa1ace61733b61d4325ec6ee808ffd/3rdparty/libprocess/src/process.cpp#L1232-L1234]. > However, more appropriate would be to send a {{500 Internal Server Error}} > given the documented behavior of these statuses: > *500 Internal Server Error* > A generic error message, given when an unexpected condition was encountered > and no more specific message is suitable. > *503 Service Unavailable* > The server is currently unavailable (because it is overloaded or down for > maintenance). Generally, this is a temporary state. > From https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_Error -- This message was sent by Atlassian JIRA (v6.3.4#6332)