$mimeType parameter in body() method sets the expects as well as sends mime type.

[BAM5]

This should be fixed so that it only sets the mime type of what is being passed in body, aka, the mime type of the data being sent.
At the very least it should be documented.

[nategood]

Agree it should be documented. In order to make it non breaking for now,
we may start by adding another optional argument to specify expects mime
type.
On Feb 24, 2014 6:38 PM, "BAM5" [email protected] wrote:

This should be fixed so that it only sets the mime type of what is being
passed in body, aka, the mime type of the data being sent.
At the very least it should be documented.

Reply to this email directly or view it on GitHubhttps://github.com//issues/119
.

[BAM5]

That would be good.
But yes, my code was not performing as expected because I set the mimeType parameter to urlencoded, because that was what the post body content was. It was a logical assumption because $mimeType clearly only applies to the body that I'm sending since it's in the body method right? And then when the server returned JSON I was unable to access $response->body like I should have. Took about 15 minutes of debugging and trace to figure out the problem.

Personally I think it should just set the mime type of the content you're passing to body(), there are other functions that set the expected return mime type, plus there's also the smart parsing from the response's content-type header.

[nategood]

Agree that this could cause unexpected behavior, will change this behavior in the next MINOR version update, 0.3.0 (see r0.3.0 branch). I have updated the docs for now on master.