Useful information on Bad Request

[FabioPinheiro]

It's very hard to figure out what is wrong when you are trying to integrate with the Roots-id's mediator.

On the HTTP response I get a 400 with {"detail":"Malformed Message"}

On the serve side logs, I see

roots-id-mediator-rootsid-mediator-1  | MalformedMessageCode.INVALID_PLAINTEXT
roots-id-mediator-rootsid-mediator-1  | INFO:     172.18.0.1:35914 - "POST / HTTP/1.1" 400 Bad Request

I don't want to go into the code to figure out how it works so I can test and print out what is wrong.

If we want to achieve interoperability we need better errors

[rodolfomiranda]

@FabioPinheiro , if that's not solved (as per de other issue) , please send me the plain message your sending.
And you are right. This code still a proof of concepts, and the handling of errors is on the TODO list!! I'll see if I can improve that a little bit.

[FabioPinheiro]

INVALID_PLAINTEXT it's already a bit more useful than only "Malformed Message"

But you don't have any other information that you can send since the library doesn't give you.

I am now waiting for the issue to be solved on sicpa-dlab/didcomm-python#93. I'm hoping that will solve my problem and I can start sending messages to roots-id/didcomm-mediator