Re: [hybi] workability (or otherwise) of HTTP upgrade

Zhong Yu <zhong.j.yu@gmail.com> Sat, 11 December 2010 01:04 UTC

Return-Path: <zhong.j.yu@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A278628C10B for <hybi@core3.amsl.com>; Fri, 10 Dec 2010 17:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.371
X-Spam-Level:
X-Spam-Status: No, score=-3.371 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jx47WqievLI for <hybi@core3.amsl.com>; Fri, 10 Dec 2010 17:04:21 -0800 (PST)
Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by core3.amsl.com (Postfix) with ESMTP id 1375228C157 for <hybi@ietf.org>; Fri, 10 Dec 2010 17:04:20 -0800 (PST)
Received: by ewy6 with SMTP id 6so3031291ewy.40 for <hybi@ietf.org>; Fri, 10 Dec 2010 17:05:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WTFz7tooPcRqYHiNpiG07rln7YJmOuGnWn0nfXCLQas=; b=S42B4vZ34GoO2kjcKLb1n7yU80Ox5qt5MMAQs5DpzyXzsAjKa6C4rDQ8yPaLyDmay1 MxqBv9ka2llTwMRBDZs+Pb8pxWhsK54nw3cciV5awqg6ebG1ar26EkHNkady93QEOr0F No8242epr4FlzS325kuuSMrw6vVabPslf1hnw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bVXjLFpTdNzfet07KokcMVT8Y0hgcVTnVgs1tXCsC0jOKJMhHpqMP2x44mwET9mtqV wV7t4A2zILMN/3ad/v4CZPVmKSLHOOEug7rtnDxQB5xKtWlRNKNmbXmwCB0BZtgR1nFo Nq96TRyTfyUSKSEcJw2puW81yvnwSqq4tb6gY=
MIME-Version: 1.0
Received: by 10.213.15.135 with SMTP id k7mr1661515eba.26.1292029552575; Fri, 10 Dec 2010 17:05:52 -0800 (PST)
Received: by 10.213.23.20 with HTTP; Fri, 10 Dec 2010 17:05:52 -0800 (PST)
In-Reply-To: <AANLkTimk5ZzWKusxM7m2eQwTu+vnqa9S__EvLZJ47OSt@mail.gmail.com>
References: <BB947F6D-15AA-455D-B830-5E12C80C1ACD@mnot.net> <81870DB1-B177-4253-8233-52C4168BE99D@apple.com> <F4D1B715-3606-4E9A-BFB2-8B7BC11BE331@mnot.net> <57D4B885-B1D8-482F-8747-6460C0FFF166@apple.com> <37A00E8D-B55C-49AD-A85C-A299C80FFF17@mnot.net> <4F2580A7-79C2-4B0A-BCE5-7FB6D9AA0ED7@apple.com> <BB31C4AB95A70042A256109D461991260583956C@XCH117CNC.rim.net> <EA41A6C7-971C-4EC8-AA6F-96363B7FDC4C@gmail.com> <73E53F19-E0E7-4ADB-B765-ABAF0B4A6736@mnot.net> <r2f0g6d7bj770kg0db5ptr027ninmckns8@hive.bjoern.hoehrmann.de> <20C2FBB9-901F-4235-AF23-EC8262585905@mnot.net> <1291905941.2315.2113.camel@ds9.ducksong.com> <4D011146.3080906@caucho.com> <AANLkTi=CKU8H5A2f7rSGZ9h5mrp=NZW0yLB9O6=MDW5i@mail.gmail.com> <AANLkTimk5ZzWKusxM7m2eQwTu+vnqa9S__EvLZJ47OSt@mail.gmail.com>
Date: Fri, 10 Dec 2010 19:05:52 -0600
Message-ID: <AANLkTim2ztPWAoOHHTLErtiJSGOcHFEAQUZK7yZ93VLH@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: Greg Wilkins <gregw@webtide.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] workability (or otherwise) of HTTP upgrade
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 11 Dec 2010 01:04:24 -0000

The two arguments are mutually strengthening each other. If cookies
are good, we better use HTTP syntax. If HTTP syntax is good, we better
as well ship cookies. I thought there is some circularity there, and
we better rethink state management in isolation. But I give up,
dependency on cookies is too strong, and HTTP syntax is probably
unavoidable.

On Fri, Dec 10, 2010 at 3:39 AM, Greg Wilkins <gregw@webtide.com> wrote:
> On 9 December 2010 20:42, Zhong Yu <zhong.j.yu@gmail.com> wrote:
>> I believe HTTP cookies shouldn't be included in WS, and I'll make that
>> case in time.
>
> If WS starts with a normal HTTP request, then I think that request
> should fully respect the current state of the art with regards to
> cookies.  It is a HTTP request and will be routed and handled by
> existing HTTP mechanisms, many of which use Cookies as part of their
> security, routing or other value add. Whatever you think of cookies as
> a design, adding additional exceptions and provisions for special HTTP
> requests is just going to add to confusion and make worse designs.
>
> If WS does not use a normal HTTP request as the handshake, then I
> don't see any need to use cookies.   I think CONNECT is not a "normal"
> HTTP request and handling of it is treated specially, so I see less
> (or zero) need for cookies with CONNECT.
>
> cheers
>