Re: [hybi] Handshake was: The WebSocket protocol issues.

Patrick McManus <mcmanus@ducksong.com> Tue, 12 October 2010 18:54 UTC

Return-Path: <mcmanus@ducksong.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 009E13A6A15 for <hybi@core3.amsl.com>; Tue, 12 Oct 2010 11:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[AWL=-0.019, 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 LQGHFlp34qFq for <hybi@core3.amsl.com>; Tue, 12 Oct 2010 11:54:27 -0700 (PDT)
Received: from linode.ducksong.com (linode.ducksong.com [64.22.125.164]) by core3.amsl.com (Postfix) with ESMTP id 0B9403A69B6 for <hybi@ietf.org>; Tue, 12 Oct 2010 11:54:27 -0700 (PDT)
Received: by linode.ducksong.com (Postfix, from userid 1000) id A7B51102A7; Tue, 12 Oct 2010 14:55:41 -0400 (EDT)
Received: from [192.168.16.226] (cpe-67-253-92-25.maine.res.rr.com [67.253.92.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by linode.ducksong.com (Postfix) with ESMTPSA id 5D0F9101F5; Tue, 12 Oct 2010 14:55:40 -0400 (EDT)
From: Patrick McManus <mcmanus@ducksong.com>
To: Scott Ferguson <ferg@caucho.com>
In-Reply-To: <4CB0A27D.9000307@caucho.com>
References: <AANLkTiksehiSp7DB17MBVBb457p6pN5E8vma6FHz1c9j@mail.gmail.com> <4CACA667.3040309@caucho.com> <4CAF9589.1060007@caucho.com> <AANLkTinnnT5Oib7FvDdZF2q_WUT8=q8KNmfkfajE0Mor@mail.gmail.com> <4CAFA043.10101@caucho.com> <AANLkTi=eo-cjBz160FN0cn53v4-CpDSYaEneqkr_ZP7k@mail.gmail.com> <AANLkTi=B1rGBgi4jYZ_TqX9Qt1xtXoyneZtztnLOkW6b@mail.gmail.com> <4CAFBD75.4020004@caucho.com> <r7gva6tv01olonop6co9ftn63dlqmhnts3@hive.bjoern.hoehrmann.de> <4CB0915A.1030400@caucho.com> <at41b6tsldo70ddhkokv8laoie5m99p35s@hive.bjoern.hoehrmann.de> <4CB0A27D.9000307@caucho.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 12 Oct 2010 14:55:25 -0400
Message-ID: <1286909725.2924.1991.camel@ds9.ducksong.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Content-Transfer-Encoding: 7bit
Cc: hybi <hybi@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [hybi] Handshake was: The WebSocket protocol issues.
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, 12 Oct 2010 18:54:28 -0000

On Sat, 2010-10-09 at 10:12 -0700, Scott Ferguson wrote:

> IP restrictions aren't practical because clients access sites from a 

IP ACLs have limited value, but I see them all the time. A friend asked
me for a little apache administration help just the other day and it
turned out he had an Apache server running a bunch of content that could
be accessed either via http-basic auth or IP ACL. The 'office' network
was in the IP ACL whitelist, other users had to login.

In his case it wasn't a shared host, but that was a coincidence.

Its real.