error messages get swallowed
Opened this issue · 0 comments
matthias-mess commented
Lines 239 to 252 in f09a160
The actual error message is in
response.text
and can't be accessed after the raise_for_status
anymore. It's hard to know on application level what went wrong if the error is just "400 bad request". It would be good if the actual error message would be part of the exception message.
After hacking the library I found out that I actually got the error message {"msg":"Message must be no more than 64k"}
from ironmq. I was spending have the day searching why my request is not working.