[hybi] -05: Overly restrictive with "Connection"

"Pat McManus @Mozilla" <mcmanus@ducksong.com> Fri, 11 February 2011 17:04 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 4D7E63A69E7 for <hybi@core3.amsl.com>; Fri, 11 Feb 2011 09:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 WPEpgza4NNs7 for <hybi@core3.amsl.com>; Fri, 11 Feb 2011 09:04:30 -0800 (PST)
Received: from linode.ducksong.com (linode.ducksong.com [64.22.125.164]) by core3.amsl.com (Postfix) with ESMTP id 036D83A6956 for <hybi@ietf.org>; Fri, 11 Feb 2011 09:04:29 -0800 (PST)
Received: by linode.ducksong.com (Postfix, from userid 1000) id 1B2EE102A8; Fri, 11 Feb 2011 12:04:44 -0500 (EST)
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 D414B10157 for <hybi@ietf.org>; Fri, 11 Feb 2011 12:04:40 -0500 (EST)
From: "Pat McManus @Mozilla" <mcmanus@ducksong.com>
To: hybi <hybi@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 11 Feb 2011 12:03:41 -0500
Message-ID: <1297443821.2401.147.camel@ds9.ducksong.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Content-Transfer-Encoding: 7bit
Subject: [hybi] -05: Overly restrictive with "Connection"
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, 11 Feb 2011 17:04:31 -0000

In client requirements (5.1), under handshake requirement #6: 
"The request MUST contain a "Connection" header whose value is equal to
"Upgrade"."

I believe that should be changed to "whose value contains the Upgrade
token" instead of the "equal" language. As currently written it
prohibits the client from concurrently using the Connection header for
other valid HTTP/1.1 purposes too, and we want to make this HTTP/1.1
compatible.

Similarly:

 "If the response lacks a Connection header or the Connection header
contains a value that is not an ASCII case-insensitive match for the
value "Upgrade", the client MUST fail the WebSocket connection." 

Again, we require an upgrade token but its ok to have other values in
there too.. in order to be http compatible we must loosen this receive
condition, and we ought to loosen the send one too.


-- 
http://www.getfirefox.com/