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

Julian Reschke <julian.reschke@gmx.de> Sat, 05 September 2015 18:09 UTC

Return-Path: <julian.reschke@gmx.de>
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 A6F0E1B3858 for <hybi@ietfa.amsl.com>; Sat, 5 Sep 2015 11:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 O0rmaj_Nqj5g for <hybi@ietfa.amsl.com>; Sat, 5 Sep 2015 11:09:06 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A48A21B3850 for <hybi@ietf.org>; Sat, 5 Sep 2015 11:09:05 -0700 (PDT)
Received: from [192.168.2.177] ([84.187.35.114]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M7kwW-1Ym77W2lo8-00vRXv; Sat, 05 Sep 2015 20:09:02 +0200
To: Anne van Kesteren <annevk@annevk.nl>, "hybi@ietf.org" <hybi@ietf.org>
References: <CADnb78iWYqqG1t+bYRtMvFifJru06JXb0=KQgfunRrXt-+8E8w@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <55EB2FBF.4080602@gmx.de>
Date: Sat, 05 Sep 2015 20:09:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CADnb78iWYqqG1t+bYRtMvFifJru06JXb0=KQgfunRrXt-+8E8w@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ePTdhHN/4+4cSMYiHV0WoLPqxnT9u9nfwECyVjJomO66jnCj8v6 nPqO7gC4KVFUQBJrJM7ThWU87NWxHMwmzFXlSYKj0NQRRLY51YEjQG+v3l4KtJRlPDPXhZy STu8JH+tHRM11jp1wOFyhI2D2jg+09bfDIjfEs7cyrDIUyue+ejX7u+NA5Rw4C2Y0RyEx7V 3ptMB8pNO60/cJVw81H9w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:stMhcMbFO9U=:hlwX+591ogykYw1d1ugy+V fSoUXzfjsnTw69DDYPmQiTNRPjj2D1J0HqkgFG7dM4pvW8GjDsVPUqpGglLKlwQ9TBMhWgrX5 oQFy60hU0nw9+MCYar6G+e6ZyVTQZdw4Jm2YzSVe7td4VOeqOC2e1OZxZeEw2+jpm2i8iT7Cn i653J9nbHkifn7a7QyrIPYILpbHPM9cZ7mj/8Kf1nUZYb02oKpm8QId14vSTEVfO+3kzPpVeR 7HZdTGRTim4j25Sou14xsZ0PN1OQhQni+nG+nB84832UdvnYEJYwMZ354YuhJxzdqFpTSG9f9 z69OeH5WmGJtGuEQqYSkVmHn97sWPVGM/dgqfGBSXuFzHtKQlOE1zJC8MNGDUC3V0uf99Basi Yx/ME8hEofx+W2aNsn1jBINFzrIp0V8Ar+aDtliYzGca5KnsQIJhtpN0DVrEd2cgyxeQA5hiq TuIN7CnKAWmQY5QH8Xd5Zp5SkV9hsucmZy9HAf+eIZHG34iKUXmfMJdSi4dpHWHvnZOADC4P4 17nX+b7zIyOlHNkAI9diD/WnLZrB+eGKPq9HuVO8v3md1jmyO5MKUYA8dpMWW5O1JR8mefhlM P8QxJbb3KGQgXbc466XGUCInEjpi9ogvZJ1hZjV0hLKIMnwgxlPfOIcqka1FlbTtaE5qRR50k uuQRJrLdMbVQYsvzX88sM8OJyMK/TuvX3rnCTQqyKx19zOgWsnQ3wV7ovko4ddXgDOgEDUNJd WIWCKjYJqbu+oo+D8F/Axhnikhv3k5DBM8WC8Q==
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/eDixdevwp_plCup3TpPyaY6pwks>
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: Sat, 05 Sep 2015 18:09:07 -0000

On 2015-09-05 19:25, Anne van Kesteren wrote:
> After the tenth protocol draft this algorithm broke a hook the API
> standard was using and those authoring the WebSocket API were never
> notified.
>
> See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27869 for details.
>
> How do you suggest this gets fixed?

The subject line is misleading. 
<https://tools.ietf.org/html/rfc6455#section-4.1>, item 12 in the second 
list is:

>    12.  The request MAY include any other header fields, for example,
>         cookies [RFC6265] and/or authentication-related header fields
>         such as the |Authorization| header field [RFC2616], which are
>         processed according to documents that define them.

Best regards, Julian