Re: Op-sec simplification

Mark Nottingham <mnot@mnot.net> Mon, 31 October 2016 22:47 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7713F129493 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 31 Oct 2016 15:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZM6dnV8HIDn for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 31 Oct 2016 15:47:14 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98E51127735 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 31 Oct 2016 15:47:13 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c1LHn-0007xx-Ja for ietf-http-wg-dist@listhub.w3.org; Mon, 31 Oct 2016 22:42:35 +0000
Resent-Date: Mon, 31 Oct 2016 22:42:35 +0000
Resent-Message-Id: <E1c1LHn-0007xx-Ja@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <mnot@mnot.net>) id 1c1LHi-0007v3-B0 for ietf-http-wg@listhub.w3.org; Mon, 31 Oct 2016 22:42:30 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <mnot@mnot.net>) id 1c1LHb-0003tW-TM for ietf-http-wg@w3.org; Mon, 31 Oct 2016 22:42:25 +0000
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 53E6422E257; Mon, 31 Oct 2016 18:41:59 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20161031053239.E9C6D12F5D@welho-filter3.welho.com>
Date: Tue, 1 Nov 2016 09:41:56 +1100
Cc: Martin Thomson <martin.thomson@gmail.com>, HTTP working group mailing list <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <842E817E-77E4-45E0-B5E3-D45F8D7AFA15@mnot.net>
References: <20161031053239.E9C6D12F5D@welho-filter3.welho.com>
To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
X-Mailer: Apple Mail (2.3251)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-8.1
X-W3C-Hub-Spam-Report: AWL=1.498, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1c1LHb-0003tW-TM 3f97d6ff85f68b75c27a101836d685d7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Op-sec simplification
Archived-At: <http://www.w3.org/mid/842E817E-77E4-45E0-B5E3-D45F8D7AFA15@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32762
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hold on -- are we layering in a new requirement to use the absolute form of the URL?

That's going to cause issues with a number of client and server side implementations that don't have control over or access to the precise form of the URL on the wire.

It also violates a MUST in 7230, 5.3.1:

"""
When making a request directly to an origin server, other than a CONNECT or server-wide OPTIONS request (as detailed below), a client MUST send only the absolute path and query components of the target URI as the request-target. If the target URI's path component is empty, the client MUST send "/" as the path within the origin-form of request-target.
"""

Cheers,



> On 31 Oct. 2016, at 4:32 pm, Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote:
> 
> | https://github.com/httpwg/http-extensions/pull/254
> | 
> | The main changes:
> | 
> |  - the .well-known resource is a flat list of origins
> 
> ( no comment about that yet. )
> 
> |  - the client only needs to acquire a .wk from the secured server
> 
> Hmm. Reading it from original and from the secured server
> gives little more verify that they really are giving same answers.
> 
> | - the draft explicitly allows HTTP/1.1
> 
> https://github.com/httpwg/http-extensions/blob/967aa51e513e4a2eea39ce6b2a37789be05c9483/draft-ietf-httpbis-http2-encryption.md#using-http-uris-over-tls
> 
> | Note that HTTP/1.1 requests MUST use the absolute form (see Section 5.3.2 of {{RFC7230}}).
> 
> Yes, I suggested that.
> 
> Example needs also to use absolute form here:
> 
> https://github.com/httpwg/http-extensions/blob/967aa51e513e4a2eea39ce6b2a37789be05c9483/draft-ietf-httpbis-http2-encryption.md#alternative-server-opt-in-auth
> 
> | GET /.well-known/http-opportunistic HTTP/1.1
> | Host: www.example.com
> 
> 
> ( I think that I mentioned that example also. )
> 
> So it should be
> 
> | GET http://www.example.com/.well-known/http-opportunistic HTTP/1.1
> | Host: www.example.com
> 
> 
> ( Seems that "Host" header is required also when absolute form is used. 
>  That I missed last time
>  https://lists.w3.org/Archives/Public/ietf-http-wg/2016OctDec/0097.html
> )
> 
> / Kari Hurtta
> 
> 

--
Mark Nottingham   https://www.mnot.net/