Re: [OAUTH-WG] HTTP/1.0 and JSON

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@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 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 library
> that can talk 1.0 or 1.1. I make an HTTP request with URI + form parameters +
> extra headers - I don't know if the "Host:" header will exist. So, can you just
> refer to the "hostname" and "port"? (Whether they are in the URI or a Host:
> header seems orthogonal to OAuth anyway?)

The MAC draft works on HTTP/1.1 requests. Using it with 1.0 is undefined.

> 
> Why do you POST application/x-www-form-urlencoded but get
> application/json?

There is a long thread somewhere... But it's the compromise we reached.

> 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?

Every modern platform has a JSON parser.

EHL

> 
> All the best,
> Tim.
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth