You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like better processing of JSON error responses. Currently when the error response is in the body of the Http response, it is not processed as json, it is stored as plain text in the exception message. This means that the user code has to parse the exception error message in order to extract the real error message. It would be easier if the json body was processed so users would not have to do it.
Currently, this is handled in JenkinsErrorHandler.java. The whole message is stored in the ErrorsHolder of RequestStatus as a plain text message. It looks like this:
I would like better processing of JSON error responses. Currently when the error response is in the body of the Http response, it is not processed as json, it is stored as plain text in the exception message. This means that the user code has to parse the exception error message in order to extract the real error message. It would be easier if the json body was processed so users would not have to do it.
Here is an example. The request:
The response:
Currently, this is handled in
JenkinsErrorHandler.java
. The whole message is stored in theErrorsHolder
ofRequestStatus
as a plain text message. It looks like this:According to this conversation, the json would be the same for all Jetty based installations.
The text was updated successfully, but these errors were encountered: