You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2016/09/21 21:34:20 UTC
[jira] [Assigned] (MESOS-6220) HTTP handler failures should result
in 500 response rather than 503 response.
[ https://issues.apache.org/jira/browse/MESOS-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler reassigned MESOS-6220:
--------------------------------------
Assignee: Benjamin Mahler
> 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
>
> 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)