IETF Logo Mail Archive

Re: Formalizing the HTTP State Tokens proposal.

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Mon, 01 April 2019 18:12 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 B28C41203F2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 1 Apr 2019 11:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=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 gopU0f7pMxy1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 1 Apr 2019 11:12:01 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4402712011C for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 1 Apr 2019 11:12:01 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hB1ND-0001oF-24 for ietf-http-wg-dist@listhub.w3.org; Mon, 01 Apr 2019 18:09:31 +0000
Resent-Date: Mon, 01 Apr 2019 18:09:31 +0000
Resent-Message-Id: <E1hB1ND-0001oF-24@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1hB1NB-0001nS-Ft for ietf-http-wg@listhub.w3.org; Mon, 01 Apr 2019 18:09:29 +0000
Received: from welho-filter3.welho.com ([83.102.41.25]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1hB1N8-0001Ek-6G for ietf-http-wg@w3.org; Mon, 01 Apr 2019 18:09:29 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter3.welho.com (Postfix) with ESMTP id 7BE30325D; Mon, 1 Apr 2019 21:09:03 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter3.welho.com [::ffff:83.102.41.25]) (amavisd-new, port 10024) with ESMTP id 4jocStjhVVG3; Mon, 1 Apr 2019 21:09:02 +0300 (EEST)
Received: from kasvihuone.keh.iki.fi (89-27-39-95.bb.dnainternet.fi [89.27.39.95]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPS id 3AB252309; Mon, 1 Apr 2019 21:08:56 +0300 (EEST)
In-Reply-To: <CAKXHy=d3xmsaCGYmnvDQXegMNf1j0gLbpRiLCaT1yr1r=jeueA@mail.gmail.com>
References: <CAKXHy=d3xmsaCGYmnvDQXegMNf1j0gLbpRiLCaT1yr1r=jeueA@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Date: Mon, 01 Apr 2019 21:08:56 +0300
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Mike West <mkwst@google.com>
X-Mailer: ELM [version ME+ 2.5 PLalpha49+]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20190401180903.7BE30325D@welho-filter3.welho.com>
X-W3C-Hub-Spam-Status: No, score=-4.8
X-W3C-Hub-Spam-Report: AWL=0.824, BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hB1N8-0001Ek-6G 28e3442bf5bf48cde5f2725c47445a30
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Formalizing the HTTP State Tokens proposal.
Archived-At: <https://www.w3.org/mid/20190401180903.7BE30325D@welho-filter3.welho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36492
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

3.2.  Requests and Responses
https://tools.ietf.org/html/draft-west-http-state-tokens-00#section-3.2

|   This document relies upon the definitions of "request" and "response"
|   found in [Fetch].
|
|   A request's delivery scope can be obtained as follows:
|
|   1.  Let "request-origin" be the request's "origin", and "target-
|       origin" be the request's "URL"'s "origin".
|
|   2.  If the request was generated by the user agent as a response to
|       direct user interaction with the user agent (e.g. the user typed
|       an address into the agent's address bar, clicked a bookmark, or
|       etc.), return "same-origin".
|
|   3.  If "request-origin" is same-origin with "target-origin", return
|       "same-origin".
|
|   4.  If "request-origin"'s registrable domain is the same as "target-
|       origin"'s registrable domain, return "same-site".
|
|   5.  Return "cross-site".


Is delivery=same-site intended to cause Sec-Http-State request field
to be send about same requests than Cookies with SameSite attribute?

SameSite seems use definition "site for cookies" for that. How that
compare to "request-origin" ?

5.2.  "Same-site" and "cross-site" Requests
https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-02#section-5.2

|   2.  Let "site" be "request"'s client's "site for cookies" (as defined
|       in the following sections).
|
|   3.  Let "target" be the registered domain of "request"'s current url.
|
|   4.  If "site" is an exact match for "target", return "same-site".

5.2.1.  Document-based requests
https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-02#section-5.2.1

|   For a document displayed in a top-level browsing context, we can stop
|   here: the document's "site for cookies" is the top-level site.

 (and so on)


I failed interpret how Fetch defines request's "origin"

https://fetch.spec.whatwg.org/#concept-request-origin

https://html.spec.whatwg.org/multipage/origin.html#concept-origin


Specially nested browsing contexts (iframes and so on).


/ Kari Hurtta

v2.23.0 | Report a Bug | By Email