@m4dcoder closed #5513 because of CLA issues and opened this one. Could you please review.
Thanks!

@m4dcoder looks your previous review comments in #5513 were addressed, but please comment if you think we need something else here before merging it tomorrow.

I have not dug too deeply into this PR, but at face value this may fix Issue #4853 as well.

@sravs-dev Is there a unit test that shows an example for unsupported content type for x-www-form-urlencoded and how failure is handled?

@armab @m4dcoder When I try to give invalid content/body for x-www-form-urlencoded mimetype, the request building itself fails like this failure in unit test.
Also, I noticed there is an existing test case for un supported content type here . I believe the existing test case would suffice. Let me know your thoughts.

@m4dcoder Could you please take a look at the comment above?

@sravs-dev What I meant on unsupported content type for x-www-form-urlencoded is a use case where six.ensure_str returns an error and how that error is handled? Is this possible to test?

six.ensure_str

@m4dcoder Thanks for your reply. six.ensure_str takes bytes input, I dont think we can simulate this input as its sent by the API internally. We can only send the payload as key value pair for x-www-form-urlencoded content type.
If six. ensure_str throws error, I guess we would get 500 error similar to what I faced in this issue .
I will go ahead and revert the test case that's passing invalid data to the API.

@armab @m4dcoder On the latest commit, all CI Checks have passed except Python 3.8 chunk 1 which is failing in other PRs as well, so it's not related to my changes.

Merged! Thanks everyone 👍