In case of error response (ex. SoapFault) the Zimbra error cause (code) and message is not easily available. We can only read raw HTTP response string and parse it.
I think that Client\Http should catch the error in doRequest, and try to extract the cause and wrap it in a new, more friendly, exception.
alessiosais
commented
6 years ago
In case of error response (ex. SoapFault) the Zimbra error cause (code) and message is not easily available. We can only read raw HTTP response string and parse it. I think that Client\Http should catch the error in doRequest, and try to extract the cause and wrap it in a new, more friendly, exception.