Re: [hybi] Why HTTP Compliant

"Simon Pieters" <simonp@opera.com> Wed, 02 June 2010 07:51 UTC

Return-Path: <simonp@opera.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 E5DB43A6968 for <hybi@core3.amsl.com>; Wed, 2 Jun 2010 00:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 CxoGJ3eMrrF5 for <hybi@core3.amsl.com>; Wed, 2 Jun 2010 00:51:53 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id B54523A67EC for <hybi@ietf.org>; Wed, 2 Jun 2010 00:51:52 -0700 (PDT)
Received: from simon-pieterss-macbook.local (c-1799e355.410-6-64736c14.cust.bredbandsbolaget.se [85.227.153.23]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o527pbPI023038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Jun 2010 07:51:38 GMT
Content-Type: text/plain; charset="utf-8"; format="flowed"; delsp="yes"
To: Greg Wilkins <gregw@webtide.com>
References: <AANLkTikzNjRse7cK8hl7eX0zWL3xP0xgbGTV8hz8RruH@mail.gmail.com> <op.vdmg9uenidj3kv@simon-pieterss-macbook.local> <AANLkTil1gofHSKy1laRnudnZePhuDnAP53OZrq_b-kR5@mail.gmail.com>
Date: Wed, 02 Jun 2010 09:51:36 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: Simon Pieters <simonp@opera.com>
Message-ID: <op.vdnxf7mridj3kv@simon-pieterss-macbook.local>
In-Reply-To: <AANLkTil1gofHSKy1laRnudnZePhuDnAP53OZrq_b-kR5@mail.gmail.com>
User-Agent: Opera Mail/10.53 (MacIntel)
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] Why HTTP Compliant
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, 02 Jun 2010 07:51:54 -0000

On Tue, 01 Jun 2010 17:04:55 +0200, Greg Wilkins <gregw@webtide.com> wrote:

> Simon,
>
> I agree that there are parts of the spec that imply arbitrary headers
> are acceptable,
> but it also says:
>
>   Fields in the handshake are sent by the client in a random order; the
>    order is not meaningful.
>
>    Additional fields are used to select options in the WebSocket
>    protocol.  The only options available in this version are the ...

This text is non-normative.


> Ian has indicated that this means that the presence of other headers  
> means that
> the handshake should fail.

Indications from the editor are also non-normative. :-)


> It would be really good if I have misunderstood what he has said about  
> this, but
> at least some implementations of chromium do implement a ban on extra  
> headers.

Maybe you could file a bug? http://code.google.com/p/chromium/issues/list


> But I can't tell you exactly what versions of the draft they implement

It looks like -75 in chrome dev 6.0.408.1.



> (gee a
> ws version  string or user-agent header would be really really  
> useful!!!!!!)

I don't see how it would help you in this case (you would still have to  
write the same code to make Chrome happy).

-- 
Simon Pieters
Opera Software