IETF Logo Mail Archive

Re: [hybi] Web sockets and existing HTTP stacks

Greg Wilkins <gregw@webtide.com> Wed, 03 February 2010 04:50 UTC

Return-Path: <gregw@webtide.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 BB7493A6829 for <hybi@core3.amsl.com>; Tue, 2 Feb 2010 20:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.504
X-Spam-Level:
X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599]
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 fInFbyAS3TB4 for <hybi@core3.amsl.com>; Tue, 2 Feb 2010 20:50:45 -0800 (PST)
Received: from mail-yx0-f174.google.com (mail-yx0-f174.google.com [209.85.210.174]) by core3.amsl.com (Postfix) with ESMTP id EB1393A67FA for <hybi@ietf.org>; Tue, 2 Feb 2010 20:50:44 -0800 (PST)
Received: by yxe4 with SMTP id 4so958612yxe.32 for <hybi@ietf.org>; Tue, 02 Feb 2010 20:51:22 -0800 (PST)
Received: by 10.101.5.37 with SMTP id h37mr9126422ani.188.1265172682649; Tue, 02 Feb 2010 20:51:22 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 16sm4469474gxk.7.2010.02.02.20.51.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Feb 2010 20:51:21 -0800 (PST)
Message-ID: <4B6900C3.5090005@webtide.com>
Date: Wed, 03 Feb 2010 15:51:15 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Maciej Stachowiak <mjs@apple.com>
References: <557ae280911171402v7546e5e7n93a1e57f87dc10e5@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> <ad99d8ce1002012139l3b8f525bj9caf7861332f3d18@mail.gmail.com> <1427E183-FDBC-4854-9455-B93AB28DAB03@apple.com> <ad99d8ce1002012343n132169f8wbaacc1cf4efe2f87@mail.gmail.com> <31123817-6D3F-489D-9F48-109AC93E6769@apple.com>
In-Reply-To: <31123817-6D3F-489D-9F48-109AC93E6769@apple.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Wed, 03 Feb 2010 04:50:45 -0000

Maciej Stachowiak wrote:

> OK, just to clarify, are you saying that it's specifically the
> constraint on header ordering that is a problem? I'm trying to figure
> out which specific requirements are problematic and why. For example, is
> the requirement to have some special text in the status line acceptable?

Maciej,

It is mainly the header ordering and somewhat the case sensitivity.

I've got no problem with the websocket server requiring special
content in the status line reason.    However some existing servers
may have an issue as I have seen that some - in response to CRLF
injection attacks on the reason string - ignore any passed value
for the reason string.   But I think fixes for that will in general
be a lot less ugly than a fix for header ordering.

cheers

v2.23.0 | Report a Bug | By Email