On Thu, 2011-06-16 at 04:43 -0400, Tim Brody wrote:
> On Wed, 15 Jun 2011 11:45:28 -0400, Justin Richer
> wrote:
> >> > I couldn't find a conclusion to the May 2010 discussions about using
> >> > x-www-
> >> > form-urlencoded vs. json nor a rationale in the spec for using JSON.
> >> > Why do I
> >
On Wed, 15 Jun 2011 11:45:28 -0400, Justin Richer
wrote:
>> > I couldn't find a conclusion to the May 2010 discussions about using
>> > x-www-
>> > form-urlencoded vs. json nor a rationale in the spec for using JSON.
>> > Why do I
>> > need to add a JSON lexer/parser to my library just to get key-
> > I couldn't find a conclusion to the May 2010 discussions about using x-www-
> > form-urlencoded vs. json nor a rationale in the spec for using JSON. Why do
> > I
> > need to add a JSON lexer/parser to my library just to get key-value pairs
> > that
> > can be represented by form-urlencoded?
> -Original Message-
> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
> Of Tim Brody
> Sent: Wednesday, June 15, 2011 5:42 AM
> To: oauth@ietf.org
> Subject: [OAUTH-WG] HTTP/1.0 and JSON
>
> Hi All,
>
> I'm the author of this
Hi All,
I'm the author of this Perl library for signing OAuth 1.0 requests:
http://search.cpan.org/~timbrody/LWP-Authen-OAuth-1.01/
I've been asked about OAuth 2.0 so have scanned through the spec and
joined this list :-)
The MAC-signing draft section 1.2 refers to "Host:" but I have an HTTP
li