Re: [hybi] #1: HTTP Compliance

Greg Wilkins <gregw@webtide.com> Mon, 17 May 2010 12:35 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 060133A69C1 for <hybi@core3.amsl.com>; Mon, 17 May 2010 05:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.618
X-Spam-Level:
X-Spam-Status: No, score=-0.618 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_20=-0.74]
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 JoaSw1ObZpoU for <hybi@core3.amsl.com>; Mon, 17 May 2010 05:35:32 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 74B9728C123 for <hybi@ietf.org>; Mon, 17 May 2010 05:28:03 -0700 (PDT)
Received: by wyb42 with SMTP id 42so2534752wyb.31 for <hybi@ietf.org>; Mon, 17 May 2010 05:27:51 -0700 (PDT)
Received: by 10.227.156.19 with SMTP id u19mr4739654wbw.167.1274099271186; Mon, 17 May 2010 05:27:51 -0700 (PDT)
Received: from [192.168.0.100] ([88.43.234.116]) by mx.google.com with ESMTPS id l23sm40397805wbb.20.2010.05.17.05.27.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 17 May 2010 05:27:50 -0700 (PDT)
Message-ID: <4BF13640.8010704@webtide.com>
Date: Mon, 17 May 2010 14:27:44 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
References: <068.d07026741c6694cd80652d2a7d34f236@tools.ietf.org> <4BF106AD.6020506@webtide.com> <A42E692A-7210-4FF1-AB4F-CFB3E8C38756@apple.com> <4BF116A8.4080501@webtide.com> <9CFFE5E7-305E-4FDA-A14D-1616FE2E7D8A@apple.com>
In-Reply-To: <9CFFE5E7-305E-4FDA-A14D-1616FE2E7D8A@apple.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Mon, 17 May 2010 12:35:33 -0000

On 17/05/10 12:35, Maciej Stachowiak wrote:

> if WebSocket clients followed up a refused WebSocket upgrade 
> with HTTP requests, however, the client protocol does not
> allow this currently, so it is not at this time a practical problem.

It is a circular argument to say that HTTP non-compliance is not a
problem because the current protocol forbids HTTP compliance.


I'm saying that the protocol should not be allowed
to forbid HTTP compliance.

Furthermore, I've provided many examples where it is impossible
for a server to actually respect any such compliance ban.

Finally I've also provided many examples where compliance
would also be a benefit (for authentication etc.)


regards