Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies

Anne van Kesteren <annevk@annevk.nl> Wed, 16 September 2015 08:44 UTC

Return-Path: <annevk@annevk.nl>
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 5C8561B38EC for <hybi@ietfa.amsl.com>; Wed, 16 Sep 2015 01:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Level:
X-Spam-Status: No, score=-2.078 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, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 JD2qIs2g2BXU for <hybi@ietfa.amsl.com>; Wed, 16 Sep 2015 01:44:01 -0700 (PDT)
Received: from homiemail-a37.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) by ietfa.amsl.com (Postfix) with ESMTP id 33C321B38E2 for <hybi@ietf.org>; Wed, 16 Sep 2015 01:44:01 -0700 (PDT)
Received: from homiemail-a37.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a37.g.dreamhost.com (Postfix) with ESMTP id E1634404003 for <hybi@ietf.org>; Wed, 16 Sep 2015 01:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; s=annevk.nl; bh=qrPQXFw1fv1vTFUAGFvdO4XD8Y4=; b=O0 ZfUgBaB/P24uJwnI8a1hwl0Qa3Jy5SWXJGd4kgQKsaEo6z9NGLJhdxu4GITx9z98 RDXi1QUvSeNQwWnJ6eKSwdg02hgJZmU17d0GS7UTnIPcSfStfUvPXuUdX8F25DTr xOx6uE03iZFqboXAutSlmyGJme7ec1FvE624ghbr8=
Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com [209.85.160.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a37.g.dreamhost.com (Postfix) with ESMTPSA id C60B6404001 for <hybi@ietf.org>; Wed, 16 Sep 2015 01:44:00 -0700 (PDT)
Received: by ykdt18 with SMTP id t18so191686703ykd.3 for <hybi@ietf.org>; Wed, 16 Sep 2015 01:44:00 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.170.209.144 with SMTP id a138mr27286595ykf.5.1442393040156; Wed, 16 Sep 2015 01:44:00 -0700 (PDT)
Received: by 10.37.50.2 with HTTP; Wed, 16 Sep 2015 01:43:59 -0700 (PDT)
In-Reply-To: <CAH9hSJbSn5d5AGVW79oYusjoTe345LrVd65e9Bseo4MVcOe-sg@mail.gmail.com>
References: <CADnb78iWYqqG1t+bYRtMvFifJru06JXb0=KQgfunRrXt-+8E8w@mail.gmail.com> <55EB2FBF.4080602@gmx.de> <CADnb78hy8zG_PuOY9X0wtyJLqOH=D8BHyTnqjgwXtze3UmG9ZA@mail.gmail.com> <CAH9hSJbSn5d5AGVW79oYusjoTe345LrVd65e9Bseo4MVcOe-sg@mail.gmail.com>
Date: Wed, 16 Sep 2015 10:43:59 +0200
Message-ID: <CADnb78hzLQ2UdHiOptOV2BkKd3BExjiZyQys+J3Xcxo3_DMKug@mail.gmail.com>
From: Anne van Kesteren <annevk@annevk.nl>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/gBwNJTEKrL19GDopYvHvck-YBog>
Cc: Julian Reschke <julian.reschke@gmx.de>, "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies
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:44:02 -0000

On Wed, Sep 16, 2015 at 10:20 AM, Takeshi Yoshino <tyoshino@google.com> wrote:
> It's not expecting any argument explicitly, but given the history of the
> spec, I think we should just proceed to influence this by e.g.:
>
> Replace the second sentence of the step 9 of
> https://html.spec.whatwg.org/multipage/comms.html#dom-websocket with
>
> When processing the step 12 of the requirements for an opening handshake
> from a client described in the <a
> href="https://tools.ietf.org/html/rfc6455#section-4.1">"Client Requirements"
> section of  the WebSocket protocol specification</a>, include a Cookie
> header whose value is the cookie-string computed from the user's cookie
> store and the URL url; for these purposes this is not a "non-HTTP" API.
> [WSP] [COOKIES]

By "given the history of the spec" do you mean that we should not
expect a clean fix to appear anytime soon on the IETF side and instead
just use this monkey patch? I guess that's fine, it just seems far
from ideal, especially given that it was done properly until draft
eleven.


-- 
https://annevankesteren.nl/