JSON payload type not recognized until switched

[djromberg]

POST requests with JSON payload initially do not work if the request body type hasn't been touched. It defaults to JSON but it needs to be explicitly deselected and selected in order to work. An initial request using the default parameters (POST method and JSON body type) results in "Expected request with Content-Type: application/json" within an example service. When the body type is touched - e.g. changed from JSON to CUSTOM and back to JSON, everything works as expected and the target service is contacted with the correct Content-Type header.

It could be that the behavior of the mentioned example service is not correct, however, the RESTED client should not behave differently when being used for the first time with defaults - in comparison to setting these values explicitly.

This issue is probably related to #186 and #172. It should provide a bit more context and another hint to improve this awesome tool :)