Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion This request requires HTTP authentication

Received: by 10.204.141.4 with SMTP id k4mr1995767bku.6.1336433778894;
        Mon, 07 May 2012 16:36:18 -0700 (PDT)
X-BeenThere: healthgraph@googlegroups.com
Received: by 10.204.129.208 with SMTP id p16ls2966260bks.7.gmail; Mon, 07 May
 2012 16:36:17 -0700 (PDT)
Received: by 10.204.152.217 with SMTP id h25mr1998735bkw.3.1336433776899;
        Mon, 07 May 2012 16:36:16 -0700 (PDT)
Received: by 10.204.152.217 with SMTP id h25mr1998734bkw.3.1336433776868;
        Mon, 07 May 2012 16:36:16 -0700 (PDT)
Return-Path: <christopher.barr...@runkeeper.com>
Received: from mail-lpp01m010-f50.google.com (mail-lpp01m010-f50.google.com [209.85.215.50])
        by gmr-mx.google.com with ESMTPS id hy18si23355615bkc.2.2012.05.07.16.36.16
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 07 May 2012 16:36:16 -0700 (PDT)
Received-SPF: pass (google.com: domain of christopher.barr...@runkeeper.com designates 209.85.215.50 as permitted sender) client-ip=209.85.215.50;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of christopher.barr...@runkeeper.com designates 209.85.215.50 as permitted sender) smtp.mail=christopher.barr...@runkeeper.com; dkim=pass header...@runkeeper.com
Received: by lahm15 with SMTP id m15so1318531lah.9
        for <healthgraph@googlegroups.com>; Mon, 07 May 2012 16:36:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=runkeeper.com; s=google;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=+wfKs3gcgiTe6JWJh5HOG6GtPsR1X8CyFbD5IyhILjc=;
        b=O8rwyRcefoTxvfGpwY2G/eXT0YvX3g3kp6pn9ogXDaBpecyjJvtz3ghw0MkNBXL6JB
         6/G1HcO0zzqkXIrL3yCvdvdPDtlV9fPQJ50yhZ11K7tYBHAouIM766hwzuZ6R3vNhN7I
         +9SYmiNoP9FipXD4UbG8HaLMBaKswa79WkwaQ=
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:x-gm-message-state;
        bh=+wfKs3gcgiTe6JWJh5HOG6GtPsR1X8CyFbD5IyhILjc=;
        b=V+j1cg4Z2kgImKy7mOESrwH6Fsom0WNl8TX5OB+DVBqiKIF23j+kxrGMbRuT1UxYTa
         iFAXoI6r6ITiUyxjJM731bqa1PzdCX8yE3ujLVZYgbT7AhAIhExTvSPr70StmWXeA3B9
         0yUbYZSYfgehSF38jlt258SoZf37TEFXlH15P/ACFaNsTFW5uv/PzrUNfnRsCi+3xeQ6
         ggZF0TAwXK80t6ubwJq4I+PJtKfbcGimgTC1seI6W8HKZGKEIXgspuQH7Pl0wjCqDX4s
         mmC4AU91BNK5baZ1lEbAxS6fyZOaKiRuzRFQadXHqe/D26GYlixNGcrygzFgECuIHm20
         bHZQ==
Received: by 10.152.145.169 with SMTP id sv9mr15749623lab.12.1336433776400;
 Mon, 07 May 2012 16:36:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.129.229 with HTTP; Mon, 7 May 2012 16:35:56 -0700 (PDT)
In-Reply-To: <3935471.1022.1336433003654.JavaMail.geo-discussion-forums@vbws2>
References: <3935471.1022.1336433003654.JavaMail.geo-discussion-forums@vbws2>
From: Christopher Barratt <christopher.barr...@runkeeper.com>
Date: Mon, 7 May 2012 19:35:56 -0400
Message-ID: <CAPFaB4yASBpkzTWAKDB78=hdezcf-RjzDbCeZL2JcedvoOZ...@mail.gmail.com>
Subject: Re: This request requires HTTP authentication
To: healthgraph@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8f23509782184f04bf7abc64
X-Gm-Message-State: ALoCoQmYDRWsRWTUG5LDHMZQc0U3y6Zz0mz9oyYaoiCdjiv9ZWpI3xoGHcB3wFhOEyLNlfqCGA9e

--e89a8f23509782184f04bf7abc64
Content-Type: text/plain; charset=UTF-8

"invalid_request" is an OAuth error:

* From the authorization endpoint, it means that the "response_type" was
something other than "code";

* From the token endpoint, it means that one or more of the following are
incorrect: client_id, client_secret, code, and/or redirect_uri.

If you send me your client ID, I can look at our logs to see which case is
occurring.  Common causes are:

* Attempt to re-use an authorization code (they expire as soon as they are
converted to access tokens); or,
* Not passing the same redirect_uri to both endpoints.

-- Chris

On Mon, May 7, 2012 at 7:23 PM, real_ate <and...@bloo.ie> wrote:

> Hi All,
>
> I've just figured out the API and made my first successful weight update
> (go me!). But now I'm having a few troubles. I was developing locally and
> after I pushed my code to my live site I tried to submit another weight
> update but I get a 401 error with the text "This request requires HTTP
> authentication".
>
> I looked into the issue a bit more and it seems that I wasn't actually
> being returned an access_token, I was getting and error back with the text
> : "invalid_request".
>
> I don't know what to do. It might be related to the fact that I tried
> removing the app from my Runkeeper account to see if I needed to add it
> again or something. Is removing an app permanent or something?
>
> The app is hosted at http://weighttrail.com/ if you want to see for
> yourself. It just adds a weight to your profile at the moment when you
> submit.
>
> Any help would be greatly appreciated,
> Cheers!
>

--e89a8f23509782184f04bf7abc64
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

&quot;invalid_request&quot; is an OAuth error:<div><br></div><div>* From th=
e authorization endpoint, it means that the &quot;response_type&quot; was s=
omething other than &quot;code&quot;;</div><div><br></div><div>* From the t=
oken endpoint, it means that one or more of the following are incorrect: cl=
ient_id, client_secret, code, and/or redirect_uri.</div>

<div><br></div><div>If you send me your client ID, I can look at our logs t=
o see which case is occurring. =C2=A0Common causes are:</div><div><br></div=
><div>* Attempt to re-use an authorization code (they expire as soon as the=
y are converted to access tokens); or,</div>

<div>* Not passing the same redirect_uri to both endpoints.</div><div><br><=
/div><div>-- Chris</div><div><div><br><div class=3D"gmail_quote">On Mon, Ma=
y 7, 2012 at 7:23 PM, real_ate <span dir=3D"ltr">&lt;<a href=3D"mailto:andr=
e...@bloo.ie" target=3D"_blank">and...@bloo.ie</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi All, =C2=A0<div><br></div><div>I&#39;ve j=
ust figured out the API and made my first successful weight update (go me!)=
. But now I&#39;m having a few troubles. I was developing locally and after=
 I pushed my code to my live site I tried to submit another weight update b=
ut I get a 401 error with the text &quot;This request requires HTTP authent=
ication&quot;.=C2=A0</div>

<div><br></div><div>I looked into the issue a bit more and it seems that I =
wasn&#39;t actually being returned an access_token, I was getting and error=
 back with the text : &quot;invalid_request&quot;.=C2=A0</div><div><br></di=
v>

<div>I don&#39;t know what to do. It might be related to the fact that I tr=
ied removing the app from my Runkeeper account to see if I needed to add it=
 again or something. Is removing an app=C2=A0permanent=C2=A0or something?=
=C2=A0</div>
<div>
<br></div><div>The app is hosted at=C2=A0<a href=3D"http://weighttrail.com/=
" target=3D"_blank">http://weighttrail.com/</a> if you want to see for your=
self. It just adds a weight to your profile at the moment when you submit.=
=C2=A0</div>

<div><br></div><div>Any help would be greatly appreciated,=C2=A0</div><div>=
Cheers!=C2=A0</div></blockquote></div><br></div></div>

--e89a8f23509782184f04bf7abc64--