Support for OAUth2 providers that have HTTP instead of JSON authentication responses

[GoogleCodeExporter]

According to the OAUth2 speciification, the result of an authentication token 
should be a JSON body. There are however OAUth2 providers that provide an HTTP 
form response (access_token=token&token_type=). GitHub's API is one where I 
encountered this. I've heard that Facebook has the same problem.

The attached patch adds support for form field responses; It looks at the 
response headers to determine whether JSON or form fields should be used.

Original issue reported on code.google.com by i...@egeniq.com on 3 Sep 2011 at 9:30

Attachments:

• GTMOAuth2.patch

[GoogleCodeExporter]

http://code.google.com/p/gtm-oauth2/source/detail?r=57

Original comment by grobb...@google.com on 9 Sep 2011 at 9:59

• Changed state: Fixed