Re: [hybi] Web sockets and existing HTTP stacks

Roberto Peon <fenix@google.com> Tue, 02 February 2010 05:39 UTC

Return-Path: <fenix@google.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 C9E893A68EA for <hybi@core3.amsl.com>; Mon, 1 Feb 2010 21:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.978
X-Spam-Level:
X-Spam-Status: No, score=-105.978 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Zf228ql2Y8i0 for <hybi@core3.amsl.com>; Mon, 1 Feb 2010 21:39:09 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id EF7163A67D9 for <hybi@ietf.org>; Mon, 1 Feb 2010 21:39:08 -0800 (PST)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id o125dh20021007 for <hybi@ietf.org>; Tue, 2 Feb 2010 05:39:44 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265089184; bh=7HVtuiacpgXyAsyNJzfSVdbdBgw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=j6nx5xyU/6o4fGOEshDz68fEnNuOWQDzRcP/E1DVLy35u7KiDvEJ+WBO4wSA2N5TN VnuUhzv5Rz7a1wk6R7Y8A==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=QfXut9+MjwrSFPQ2O7IZ7M6/UUYsSh1FiQqXTp/B0DqE+AJLmTaLXRGrUxlXJfQZk JilSelRkTqkD4tPCrlDNA==
Received: from pxi38 (pxi38.prod.google.com [10.243.27.38]) by wpaz37.hot.corp.google.com with ESMTP id o125dfEj014698 for <hybi@ietf.org>; Mon, 1 Feb 2010 21:39:42 -0800
Received: by pxi38 with SMTP id 38so5085129pxi.28 for <hybi@ietf.org>; Mon, 01 Feb 2010 21:39:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.118.20 with SMTP id q20mr210265wfc.135.1265089181226; Mon, 01 Feb 2010 21:39:41 -0800 (PST)
In-Reply-To: <4B67A237.2040505@webtide.com>
References: <557ae280911171402v7546e5e7n93a1e57f87dc10e5@mail.gmail.com> <557ae280911200711i5493e654k67c1f5f07336bfb9@mail.gmail.com> <Pine.LNX.4.62.0912032347360.15540@hixie.dreamhostps.com> <4B2C1D52.9020505@webtide.com> <5c902b9e0912181640n497169cdrfa71f9a2908e6ef3@mail.gmail.com> <20091219005442.GA10949@shareable.org> <4B2C287E.1030006@webtide.com> <Pine.LNX.4.64.1001310835410.3846@ps20323.dreamhostps.com> <4B67A237.2040505@webtide.com>
Date: Mon, 01 Feb 2010 21:39:40 -0800
Message-ID: <ad99d8ce1002012139l3b8f525bj9caf7861332f3d18@mail.gmail.com>
From: Roberto Peon <fenix@google.com>
To: Greg Wilkins <gregw@webtide.com>
Content-Type: multipart/alternative; boundary="001636e0b7db419823047e9787cf"
X-System-Of-Record: true
Cc: hybi@ietf.org
Subject: Re: [hybi] Web sockets and existing HTTP stacks
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: Tue, 02 Feb 2010 05:39:11 -0000

On Mon, Feb 1, 2010 at 7:55 PM, Greg Wilkins <gregw@webtide.com> wrote:

> Ian Hickson wrote:
>
> > Similarly, the server, when parsing
> > the headers in "HTTP" mode, is unaffected by the order -- and indeed, the
> > Web Socket spec doesn't require _anything_ from the server in terms of
> > parsing the client request. You can completely ignore it for all the spec
> > cares. All that matters is that you send back a specific handshake. But
> if
> > you're sending back the handshake, then you're a Web Socket server, so
> why
> > do we need to follow HTTP rules? We've already established the client is
> a
> > Web Socket client, so what on earth is the point of using HTTP rules?
>
> We need to follow HTTP rules because we are in a HTTP server
> that has implemented the HTTP standard and until the CRLF
> is sent after the 101 response, HTTP rules OK!
>

Ian-- I know that I'd kick scream and generally raise hell about putting
that in our little proxy were it not HTTP compliant until the end of the 101
response.
-=R


>
>
> You think we are making up the difficulties we are having with this?
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>