[hybi] Fwd: Web sockets and existing HTTP stacks

Christian Biesinger <cbiesinger@gmail.com> Fri, 20 November 2009 15:08 UTC

Return-Path: <cbiesinger@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 1E15A3A68CC for <hybi@core3.amsl.com>; Fri, 20 Nov 2009 07:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2c6Cuvbjb+sD for <hybi@core3.amsl.com>; Fri, 20 Nov 2009 07:08:47 -0800 (PST)
Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com []) by core3.amsl.com (Postfix) with ESMTP id E26AB3A68C7 for <hybi@ietf.org>; Fri, 20 Nov 2009 07:08:46 -0800 (PST)
Received: by fxm7 with SMTP id 7so3837084fxm.29 for <hybi@ietf.org>; Fri, 20 Nov 2009 07:08:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=AlwkMzY0eKEtFIMubvOUhgx9wzvM4xf3wfv1OcNqPXw=; b=DuDEKC8bH/ac22W0itwxQDTu75OdmQGkTx6sE9rhvqJqdIw+QKinWyTUE2ik3oDmah q2+7s3zZMvkcp43ADyvOKWEBZyi3RjmGP90YLoN+4XviAfsygvj3OCSBRwAgUcZBXxet FEete7FrB3llqKmWK/87sOvDZQJ6iF1SSmUj0=
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; b=IySNazeZsMfdBJYCAq9n8Fv+NrglGQN7PpMeBvaoiiuG27GBpzVzb7qjIARw58t8v0 OfUL1tdI2HmbiyDIPuy1sBf/yjKUvQeqgcE6sBaJzs9XKCMBZMqK6X9CnuW3HRUwY1e0 lBeb5bugEBd6RfKNtupaL6c8IyprFgUj5mq20=
MIME-Version: 1.0
Received: by with SMTP id x9mr455874wee.0.1258729721107; Fri, 20 Nov 2009 07:08:41 -0800 (PST)
In-Reply-To: <557ae280911171402v7546e5e7n93a1e57f87dc10e5@mail.gmail.com>
References: <557ae280911171402v7546e5e7n93a1e57f87dc10e5@mail.gmail.com>
Date: Fri, 20 Nov 2009 16:08:41 +0100
Message-ID: <557ae280911200708l358293eeif999d8c1b8f6f5d8@mail.gmail.com>
From: Christian Biesinger <cbiesinger@gmail.com>
To: hybi@ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: Boris Zbarsky <bzbarsky@mit.edu>
Subject: [hybi] Fwd: 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: Fri, 20 Nov 2009 15:12:00 -0000

[resent from whatwg@whatwg.org, with slight additions here]


so I was reading the web sockets spec as well as a Firefox patch to
implement it.

Is it intentional that it is impossible to implement this spec over an
existing HTTP stack, as currently specified? In particular, due to the
strict requirements on the headers to send, it seems like you can't
really implement it with an existing HTTP stack. On the other hand,
you really do want to reuse your HTTP implementation, because
otherwise you have to reimplement all your HTTP proxy authentication,
including NTLM, GSSAPI, etc. Obviously another problem would be that
the actual bidirectional communication might be hard to fit into your
HTTP implementation, but that might be easier to work around.

I'll note that the implementation on Chromium trunk skips
authentication completely at the moment
search for 407)

Do you as the spec authors have any thoughts on this?