Re: [hybi] #1: HTTP Compliance

Willy Tarreau <w@1wt.eu> Thu, 22 July 2010 00:29 UTC

Return-Path: <w@1wt.eu>
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 362873A698B for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 17:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.426
X-Spam-Level:
X-Spam-Status: No, score=-1.426 tagged_above=-999 required=5 tests=[AWL=-3.241, BAYES_00=-2.599, FRT_PROFIT1=3.858, HELO_IS_SMALL6=0.556]
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 cnKUgqEbWg59 for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 17:29:19 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by core3.amsl.com (Postfix) with ESMTP id 1DA013A6970 for <hybi@ietf.org>; Wed, 21 Jul 2010 17:29:17 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id o6M0TSiG007633; Thu, 22 Jul 2010 02:29:28 +0200
Date: Thu, 22 Jul 2010 02:29:28 +0200
From: Willy Tarreau <w@1wt.eu>
To: Jamie Lokier <jamie@shareable.org>
Message-ID: <20100722002928.GE7174@1wt.eu>
References: <Pine.LNX.4.64.1005182105360.22838@ps20323.dreamhostps.com> <20100519013238.GB2318@shareable.org> <Pine.LNX.4.64.1007210108300.7242@ps20323.dreamhostps.com> <AANLkTik5NXkKhV+d9skXpYa_afSwthmdf=LrTbXkzwRQ@mail.gmail.com> <20100721151531.GA2990@1wt.eu> <AANLkTikjbPObJEObZWceYuC1g0bYTg+8-5eQJBWKjBr=@mail.gmail.com> <20100721154519.GA3243@1wt.eu> <20100721233834.GG14589@shareable.org> <20100722000809.GB7174@1wt.eu> <20100722002207.GI14589@shareable.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20100722002207.GI14589@shareable.org>
User-Agent: Mutt/1.4.2.3i
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] #1: HTTP Compliance
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: Thu, 22 Jul 2010 00:29:21 -0000

On Thu, Jul 22, 2010 at 01:22:07AM +0100, Jamie Lokier wrote:
> Willy Tarreau wrote:
> > Hi Jamie,
> > 
> > On Thu, Jul 22, 2010 at 12:38:34AM +0100, Jamie Lokier wrote:
> > > Willy Tarreau wrote:
> > > > On Wed, Jul 21, 2010 at 08:22:11AM -0700, Roberto Peon wrote:
> > > > > I believe Mike quoted numbers in an earlier thread.
> > > > > 
> > > > > Just to be sure we're talking about the same thing, I'm talking about the
> > > > > UPGRADE feature of HTTP generically, and not as it applies to the current
> > > > > draft Websocket spec.
> > > > 
> > > > I thought they were related to the current version since it also uses
> > > > Upgrade. Anyway, even if some don't support it yet, it will be easy
> > > > to detect bypass them based on simple rules.
> > > 
> > > Um, will it?  How would that work?
> 
> [Good description of transparent proxies at ISPs with configurable
> HTTP-aware rules on the routers.]
> 
> Ah, I thought you meant "It will be easy to bypass *broken transparent
> proxies* based on simple rules *in the WebSocket clients and/or servers*".

OK.

> I.e. how to cope when the request hits a transparent proxy that
> doesn't work and you're *not* the ISP.

This happens all the time for such ISPs with simple HTTP sites that don't
display a video or something. They know about that very fast through their
forums from complaining customers, and they fix the issue using one of the
bypass rules above. And sometimes they ask the cache editor to fix their
product because they're fed up with feeding the L7 switch with bypass rules ;-)

There are not that many ISPs in each country, I mean there are far less ISPs
than there are web sites or potential WebSocket implementers. There's a high
pressure on them to work as expected by customers.

> Failing as fast as possible, and recognising it as a failure, is
> highly desirable if we can manage that.  I don't know if we can.


That's my precise intent : fail ASAP if we know for sure it cannot work,
and don't fail for no reason when we have no proof it cannot work when
it would most likely have. Please see my proposal in another mail about
that, I think it can improve on the current handshake for that.

> It would need actual experiments on a broad cross-section of the net.

I wholeheartly agree with that. It's the first time I read about testing
before specifying on this list ! Doing so from the beginning would have
saved a lot of man-hours !

Regards,
Willy