Fork me on GitHub

@tanzoniteblack thanks, that works indeed


the problem is also that OKHttpClient adds ;charset=utf-8 to the Content-Type header of a POST request 🙁


ok, so the question now is, is there a way to retrieve the value of what yada believes is the content-type? it seems that for Content-type: application/json; charset=utf-8, yada considers the body to be application/json and parses it properly, but how do I get that value from the context? the raw request obviously has the raw header.