IETF Logo Mail Archive

Re: https at ietf.org

Yoav Nir <ynir@checkpoint.com> Thu, 07 November 2013 02:24 UTC

Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0F821E8097 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 18:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.518
X-Spam-Level:
X-Spam-Status: No, score=-10.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2ZFznpz+O4I for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 18:24:42 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id BC52311E81A7 for <ietf@ietf.org>; Wed, 6 Nov 2013 18:24:32 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id rA72OTiS017989; Thu, 7 Nov 2013 04:24:29 +0200
X-CheckPoint: {527AF863-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.106]) by DAG-EX10.ad.checkpoint.com ([169.254.3.213]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 04:24:29 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "Marco Davids (Prive)" <mdavids@forfun.net>
Subject: Re: https at ietf.org
Thread-Topic: https at ietf.org
Thread-Index: AQHO2pbmys82dyx7TkCfsyqeUBrn2JoXXCmAgAABmoCAAB+7gIABSRiAgAAjqgA=
Date: Thu, 07 Nov 2013 02:24:28 +0000
Message-ID: <C171EF13-0A85-41C1-8EC4-ED652FB6B562@checkpoint.com>
References: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com> <alpine.LRH.2.01.1311051733570.4200@egate.xpasc.com> <01P0FR4HDQNG00004G@mauve.mrochek.com> <1614F470-50C9-46B1-8242-2AB967BBD87B@hopcount.ca> <5279AD41.4020707@forfun.net> <C565008C-0258-4472-BC0B-B6C2BF459AAB@checkpoint.com> <527ADBEF.4080409@forfun.net>
In-Reply-To: <527ADBEF.4080409@forfun.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.21.18]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DB3612806A42BA4E9EF717FFA4675EF5@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 02:24:46 -0000

On Nov 6, 2013, at 4:16 PM, Marco Davids (Prive) <mdavids@forfun.net> wrote:

> On 05/11/13 20:38, Yoav Nir wrote:
>>> Enabling 'HTTP Strict Transport Security' (HSTS, RFC6797) might be a
>>> good first step.
>> HSTS means that HTTP is off (or just redirects you to HTTPS). The first S stands for "strict" and we mean it. :-)
>> 
> Well, not entirely; the redirect is strictly not part of HSTS. 

Sure it is:

7.2.  HTTP Request Type

   If an HSTS Host receives an HTTP request message over a non-secure
   transport, it SHOULD send an HTTP response message containing a
   status code indicating a permanent redirect, such as status code 301
   (Section 10.3.2 of [RFC2616]), and a Location header field value
   containing either the HTTP request's original Effective Request URI
   (see Section 9 ("Constructing an Effective Request URI")) altered as
   necessary to have a URI scheme of "https", or a URI generated
   according to local policy with a URI scheme of "https".

v2.23.0 | Report a Bug | By Email