AnsweredAssumed Answered


Question asked by tmichel on Dec 1, 2011
Latest reply on Dec 2, 2011 by trademak
Hi Folks,

Is there a way to have more "manageable" error messages when things goes wrong with REST API ?

For example, if I try to get a form for a specific task (I mean the API : /task/{taskId}/form) I get an HTTP 500 error with a message inside the HTML response page which is quite difficult to analyze without written HTML parser and so on…

The ideal way is to have a status + a message, for example :

For the REST API mentioned before, it will be better having => STATUS=404, MSG=There is no form for task 2210.

It is a proposal and I am also available to help to implement it in the REST API.

Thanks for your response,