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

Eran Hammer-Lahav <eran@hueniverse.com> Wed, 13 October 2010 22:56 UTC

Return-Path: <eran@hueniverse.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 685993A6A6C for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 15:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level:
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599]
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 ELgV8eXYuNYW for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 15:56:58 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 6F3953A6A63 for <oauth@ietf.org>; Wed, 13 Oct 2010 15:56:57 -0700 (PDT)
Received: (qmail 7987 invoked from network); 13 Oct 2010 22:58:15 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 13 Oct 2010 22:58:15 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Wed, 13 Oct 2010 15:58:01 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Breno <breno.demedeiros@gmail.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Wed, 13 Oct 2010 15:57:47 -0700
Thread-Topic: [OAUTH-WG] Request sent to http: instead of https:`
Thread-Index: ActrBN87mYxWqMOsSj2rKzKxJcarKQAJRv9A
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343D4691FAAB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <AANLkTikO0oqudUchUnpW0vSsXe0k6QKkJpxjFUU+b413@mail.gmail.com>
In-Reply-To: <AANLkTikO0oqudUchUnpW0vSsXe0k6QKkJpxjFUU+b413@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 22:56:59 -0000

Hopefully you also invalidate the token (if bearer) since it was send over an insecure channel.

EHL

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Breno
> Sent: Wednesday, October 13, 2010 11:31 AM
> To: oauth@ietf.org
> Subject: [OAUTH-WG] Request sent to http: instead of https:`
> 
> Suppose server A documents that their endpoint X is at
> https://server.example.com/x; there's no service at the corresponding http
> location for security reasons.
> 
> Client developer fatfingers URL as http://server.example.com/x
> 
> What is the correct response? I understand that this is out of scope for the
> spec, but maybe there's agreement on some guidance?
> 
> One thing one shouldn't do is serve a 302 here; it would allow defective
> clients to remain unpatched.
> 
> My preference is to simply return a bare 403 or 404 here -- after all the
> endpoint does not exist (404) or if one uses the convention that resources at
> http/https are usually identical, then http is a non-authorized method to
> access the resource (403).
> 
> Thoughts?
> 
> --
> Breno de Medeiros
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth