In most REST APIs, the host will return an explanation message when answers with an error to an HTTP request.
Having this explanation included in the log will help a lot to fix unexpected issues.
Now I must have each http request call surrounded in a try/catch block to be able to show the returned error message.
It will be acceptable if this is considered an additional functionality to be activated by using a parameter.
Originally reported by 
jvilarroig, imported from: In case of error in an http request, to log also de returned data
- assignee:
janario
- status: Open
- priority: Minor
- component(s): http-request-plugin
- label(s): jenkins, plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20260702-081740
Raw content of original issue
In most REST APIs, the host will return an explanation message when answers with an error to an HTTP request.
Having this explanation included in the log will help a lot to fix unexpected issues.
Now I must have each http request call surrounded in a try/catch block to be able to show the returned error message.
It will be acceptable if this is considered an additional functionality to be activated by using a parameter.
In most REST APIs, the host will return an explanation message when answers with an error to an HTTP request.
Having this explanation included in the log will help a lot to fix unexpected issues.
Now I must have each http request call surrounded in a try/catch block to be able to show the returned error message.
It will be acceptable if this is considered an additional functionality to be activated by using a parameter.
Originally reported by
jvilarroig, imported from: In case of error in an http request, to log also de returned data
Raw content of original issue