postJSON's Content-Type about jsoauth HOT 5 CLOSED

Does .post() do what you want it to? Your right about the header, it should have been application/json.

from jsoauth.

Here I've got a similar problem, too.

I use .request() to send a header with content type application/json to Google's OAuth service. It worked fine in 1.3, but now fails in 1.3.1. After some research, I found it's caused by the conditional expression at line 407. It detects that I manually send a Content-Type header and then blocks the init of signatureData array.

So maybe adding a content type to .getJSON() and .postJSON() will be a good way to deal with all this, I guess?

Update: I found that in my case, only adding url.query.toObject() to signatureData can pass Google's service; adding data to signatureData will also cause failure like adding nothing to signatureData… not sure if it's related to the spec you mention at line 407.

from jsoauth.

The spec says the params are signed if the content type is single part and url-form-encoded. I dont think application/json meets both those. I could be wrong but i'll revert the change for the time being.

On 29 Jul 2011, at 02:40, [email protected] wrote:

Here I've got a similar problem, too.

I use .request() to send a header with content type application/json to Google's OAuth service. It worked fine in 1.3, but now fails in 1.3.1. After some research, I found it's caused by the conditional expression at line 407. It detects that I manually send a Content-Type header and then blocks the init of signatureData array.

So maybe adding a content type to .getJSON() and .postJSON() will be a good way to deal with all this, I guess?

Reply to this email directly or view it on GitHub:
#17 (comment)

from jsoauth.

Yeah, you're right about the spec. Thanks for the explanation.
I'll find some other ways to solve my issue, so you don't have to do the reversion :)

from jsoauth.

Im going to close this for the time being

from jsoauth.