IETF Logo Mail Archive

Re: [OAUTH-WG] Request sent to http: instead of https:`

Marius Scurtescu <mscurtescu@google.com> Wed, 13 October 2010 20:54 UTC

Return-Path: <mscurtescu@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C19813A69DF for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 13:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.764
X-Spam-Level:
X-Spam-Status: No, score=-105.764 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vT9oC2+K0MAY for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 13:54:28 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 573833A69C1 for <oauth@ietf.org>; Wed, 13 Oct 2010 13:54:28 -0700 (PDT)
Received: from kpbe18.cbf.corp.google.com (kpbe18.cbf.corp.google.com [172.25.105.82]) by smtp-out.google.com with ESMTP id o9DKtiWD021581 for <oauth@ietf.org>; Wed, 13 Oct 2010 13:55:45 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287003345; bh=Xyz1pkKAV9gth2GI/O+ylsQW/ec=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=btmSr55DD4jM1yCrfB8HjEVlAztqF9FjTH1y3A/dBMfd+EIjZVL60EL9yGGUtyo/k 7xFfZIBIPnhOur2YivpqA==
Received: from gyd10 (gyd10.prod.google.com [10.243.49.202]) by kpbe18.cbf.corp.google.com with ESMTP id o9DKskAo023107 for <oauth@ietf.org>; Wed, 13 Oct 2010 13:55:43 -0700
Received: by gyd10 with SMTP id 10so2340947gyd.28 for <oauth@ietf.org>; Wed, 13 Oct 2010 13:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=IQsyvQZH1yw1Se6mGe2H1p0Y09uIpKzMzCmFYdW5UPU=; b=FMX+kC/Tb/sshRkiKTrN4XeUoV81oYz/AM1qN+qCNG22WBjpYFtd9Ef80H5HxUSLqL y5nTT48VTLnL9qObenoQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=ppD5it01L4+qBiBDOALrve9e3VIunb9jjzwx7fvUTTCMiaaWm1gLwVRne/6/vZslHM cU2WPTRx0Shoc+qgisiA==
Received: by 10.100.134.13 with SMTP id h13mr5295141and.36.1287003343401; Wed, 13 Oct 2010 13:55:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.123.19 with HTTP; Wed, 13 Oct 2010 13:55:23 -0700 (PDT)
In-Reply-To: <2CF95A0F-D113-450D-8E1A-93944F1EAE77@facebook.com>
References: <AANLkTikO0oqudUchUnpW0vSsXe0k6QKkJpxjFUU+b413@mail.gmail.com> <2CF95A0F-D113-450D-8E1A-93944F1EAE77@facebook.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 13 Oct 2010 13:55:23 -0700
Message-ID: <AANLkTinPPTg0zCzwLB4h=14FcAyKPbY1Mxzhfi+1zPrh@mail.gmail.com>
To: Paul Tarjan <paul.tarjan@facebook.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Request sent to http: instead of https:`
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 20:54:29 -0000

On Wed, Oct 13, 2010 at 1:46 PM, Paul Tarjan <paul.tarjan@facebook.com> wrote:
> At Facebook we issue an HTTP 400 with "invalid_request" as the error.
> http://graph.facebook.com/me?access_token=blah&client_id=150629244948164
> (the client_id is to enable draft-10 error messaging).

Without client_id you get a different error message (JSON as well, but
not OAuth2 compliant). Why do you need this parameter to make the
distinction?

Marius

v2.23.0 | Report a Bug | By Email