From 121790b6b1948e6cdb75fd2681aa4b02f19f351e Mon Sep 17 00:00:00 2001 From: rick Date: Fri, 1 Apr 2011 13:46:33 -0700 Subject: [PATCH] weird --- _posts/2010-04-23-oauth.markdown | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/_posts/2010-04-23-oauth.markdown b/_posts/2010-04-23-oauth.markdown index 82535f2..3d287d2 100644 --- a/_posts/2010-04-23-oauth.markdown +++ b/_posts/2010-04-23-oauth.markdown @@ -13,25 +13,25 @@ This is a description of the OAuth flow from 3rd party web sites. 1. Redirect users to a this link to request GitHub access. - GET https://github.com/login/oauth/authorize? - client_id=...& - redirect_uri=http://www.example.com/oauth_redirect + GET https://github.com/login/oauth/authorize? + client_id=...& + redirect_uri=http://www.example.com/oauth_redirect 2. If the user accepts your request, GitHub redirects back to your site with a temporary code in a code parameter. Exchange this for an access token: - POST https://github.com/login/oauth/access_token? - client_id=...& - redirect_uri=http://www.example.com/oauth_redirect& - client_secret=...& - code=... + POST https://github.com/login/oauth/access_token? + client_id=...& + redirect_uri=http://www.example.com/oauth_redirect& + client_secret=...& + code=... - RESPONSE: - access_token=... + RESPONSE: + access_token=... 3. You have the access token, so now you can make requests on the user's behalf: - GET https://github.com/api/v2/json/user/show? - access_token=... + GET https://github.com/api/v2/json/user/show? + access_token=... ## Javascript/Desktop Flow