IETF Logo Mail Archive

Re: [hybi] CONNECT handshake text

Joe Mason <jmason@rim.com> Wed, 08 December 2010 20:41 UTC

Return-Path: <jmason@rim.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 4AD063A687D for <hybi@core3.amsl.com>; Wed, 8 Dec 2010 12:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.162
X-Spam-Level:
X-Spam-Status: No, score=-6.162 tagged_above=-999 required=5 tests=[AWL=0.437, BAYES_00=-2.599, 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 N-IDQUYTVTOm for <hybi@core3.amsl.com>; Wed, 8 Dec 2010 12:41:07 -0800 (PST)
Received: from mhs03ykf.rim.net (mhs03ykf.rim.net [216.9.243.80]) by core3.amsl.com (Postfix) with ESMTP id 2088B3A6978 for <hybi@ietf.org>; Wed, 8 Dec 2010 12:41:04 -0800 (PST)
X-AuditID: 0a401fcb-b7b76ae000004026-5f-4cffedb863e0
Received: from XHT104CNC.rim.net ( [10.65.22.52]) by mhs03ykf.rim.net (RIM Mail) with SMTP id 18.93.16422.8BDEFFC4; Wed, 8 Dec 2010 15:42:32 -0500 (EST)
Received: from XCH117CNC.rim.net ([fe80::b8df:541f:9d85:9909]) by XHT104CNC.rim.net ([fe80::9520:36d8:1c40:a506%11]) with mapi; Wed, 8 Dec 2010 15:42:32 -0500
From: Joe Mason <jmason@rim.com>
To: Maciej Stachowiak <mjs@apple.com>, "ifette@google.com" <ifette@google.com>
Date: Wed, 08 Dec 2010 15:42:28 -0500
Thread-Topic: [hybi] CONNECT handshake text
Thread-Index: AcuXFMkQkIftItxXQxSR8l3wXBpEtwAA0aFg
Message-ID: <BB31C4AB95A70042A256109D4619912605839C55@XCH117CNC.rim.net>
References: <AANLkTinEXHBeaUPo4gK2CHbq7ZHYnY2PE3Vb+Oi+K1NM@mail.gmail.com> <op.vnd6ijrzidj3kv@dhcp-190.linkoping.osa> <AANLkTimWpLUFuNR62Titix5WyJumnJg7rKXty1yX7G6O@mail.gmail.com> <2AFC40EF-BC43-4709-8160-5476643CFC83@apple.com>
In-Reply-To: <2AFC40EF-BC43-4709-8160-5476643CFC83@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAgAAAZEW5C4+
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] CONNECT handshake text
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, 08 Dec 2010 20:41:08 -0000

> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of Maciej Stachowiak
> Sent: Wednesday, December 08, 2010 2:27 PM
> To: ifette@google.com
> Cc: hybi@ietf.org
> Subject: Re: [hybi] CONNECT handshake text
>
> > > The current draft says which bytes should be put on the wire exactly. I prefer the current draft over 
> > > referencing RFC2616 since doing the latter makes many variations conforming which can cause interop 
> > > problems.
> > 
> > And this was a source of contention for many people.
> 
> I believe the contention was about restricting handshake parsing to reject the client handshake unless it 
> meets very specific requirements which are tighter than the full syntax for an HTTP request.
>
> I don't think anyone had a serious objection to restricting what the client may send to be a subset of 
> RFC2616-compliant requests.

How about spelling that out specifically in the draft?  "The handshake must send the following bytes, which form a valid HTTP request as specified by [RFC2616]"

Joe

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

v2.23.0 | Report a Bug | By Email