IETF Logo Mail Archive

Re: [hybi] WebSocket and HSTS

Takeshi Yoshino <tyoshino@google.com> Wed, 16 September 2015 08:04 UTC

Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 797A01B3873 for <hybi@ietfa.amsl.com>; Wed, 16 Sep 2015 01:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 WnBt1dAU3HFc for <hybi@ietfa.amsl.com>; Wed, 16 Sep 2015 01:04:44 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22C181B3878 for <hybi@ietf.org>; Wed, 16 Sep 2015 01:04:44 -0700 (PDT)
Received: by oiww128 with SMTP id w128so115970694oiw.2 for <hybi@ietf.org>; Wed, 16 Sep 2015 01:04:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=SSjeXWiZi1eAOiWpl4b2d/R8L9ekkUzZ0k9jD0fWG78=; b=Wro1j5QC//NnSENpLW+91huIzRDSbagUSrGGXx1+OHCpuLpYud5Gv9F77yZgZ5WEI2 zwkFWisN54E4mMnxz/lC4zpUDy4uz2EcmtS923Tf3FzYIzR6AZHjzUeIaX7sYdncYzjF P3z8Oyr0EIJ7mU8Oi+NwM1i32qm7019OOQubQWQ0SvP/aFzwoksidDcp1x8lqOdxu3KA q8ljCkVXnymnX1kP/TMQEboIEjX9IbW6EatjpGRLSPddXAjE4ktElyssiUyRH7iIevDo v2cDelbpRWkssQwK6rFTaD2JH2+8aYw7UiNTZljy5cf77EQKZPZ/y3h1hZYIVoWaHBYa gvIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=SSjeXWiZi1eAOiWpl4b2d/R8L9ekkUzZ0k9jD0fWG78=; b=EbsQdjMR8TXROXJz1xVMrS3DsMr0pFkKlPqGJ0uKmv9btpFIks+qXPisF23lB3B7E8 +xLgs/0qrXQVGwLn51BcXgMQBszM/6FASHHO/6mPgdtoEpopCohELjaqYG32LapuQSvz nN34obQHaH1Jrw9f5VzxqdIBaKY+QZTRLbPvAGPncXOQThHVrujQuAhZ/WZPRcJVY+sU XEbtmN8KZrzFpxL2ZvqMinXCDG1YpfgVcBFeV9SnTvLYS3yUuOZFrI98nGztbmiBZxhh GGLZ7UGrLQl9pUmZ0BpU7PhotFsOA5qS9S151UrRd4dLHh92UUp/4hZmosQ1Sd3raRz2 Xp3Q==
X-Gm-Message-State: ALoCoQm776/wCkfNDlmtndsyLwRokfg2WZHKxImgg/HcZQQ2Xh+Ry/9BfyOYMBBuAW2U9Yjm5K9K
X-Received: by 10.202.105.74 with SMTP id e71mr21630636oic.133.1442390683467; Wed, 16 Sep 2015 01:04:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.60.4 with HTTP; Wed, 16 Sep 2015 01:04:23 -0700 (PDT)
In-Reply-To: <CADnb78hADSYgpLgsbhE18qmoAuRHGGQAgYjkYidLJL3RGBSBQw@mail.gmail.com>
References: <CADnb78hADSYgpLgsbhE18qmoAuRHGGQAgYjkYidLJL3RGBSBQw@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 16 Sep 2015 17:04:23 +0900
Message-ID: <CAH9hSJbFyzCzstu+b-qUKwexnV9czQ0My43eX=9FyU-c4tqGCA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Content-Type: multipart/alternative; boundary="001a11408c7850f0b6051fd8c0e6"
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/qimlO5_vaUaxN7FtNsdPDG16ox8>
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] WebSocket and HSTS
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2015 08:04:45 -0000

Let's just take care of it at the API spec side.

For HTTP, the Fetch algorithm has the step while the new HTTP RFCs don't.
So, aligned.

Takeshi

On Sun, Sep 6, 2015 at 2:27 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> I was wondering if you were interested in updating the protocol to
> account for HSTS or whether I should patch that in the API standard
> somehow.
>
> See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27554 for details.
>
>
> --
> https://annevankesteren.nl/
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

v2.23.0 | Report a Bug | By Email