The OAuth spec isn't clear on these points-- hence the questions. Thanks for
the great responses.
-Original Message-
From: oauth@googlegroups.com [mailto:oa...@googlegroups.com] On Behalf Of
John Kristian
Sent: Saturday, April 25, 2009 7:10 PM
To: OAuth
Subject: [oauth] Re: POST
As a rule, a server shouldn't look for OAuth parameters in the body of
a request whose content-type isn't application/x-www-form-urlencoded
(as specified by http://oauth.net/core/1.0/#consumer_req_param). In
the OpenSocial example, the client could send an XML content-type,
such as text/xml or
On Apr 24, 6:02 pm, Scott Seely sse...@myspace-inc.com wrote:
The OAuth spec is silent on how to handle section 5.2 when an HTTP PUT
|POST might be used to send in OAuth parameters AND resource content.
For example, an OpenSocial endpoint uses OAuth for authentication and
may post an XML
