IETF Logo Mail Archive

Re: [hybi] Final HTTP responses and WebSocket handshake

Gabriel Montenegro <Gabriel.Montenegro@microsoft.com> Fri, 11 February 2011 01:57 UTC

Return-Path: <Gabriel.Montenegro@microsoft.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 3F36B3A69DB for <hybi@core3.amsl.com>; Thu, 10 Feb 2011 17:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.217
X-Spam-Level:
X-Spam-Status: No, score=-10.217 tagged_above=-999 required=5 tests=[AWL=0.382, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 XCtFyN9RRAdV for <hybi@core3.amsl.com>; Thu, 10 Feb 2011 17:57:39 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 279753A69AB for <hybi@ietf.org>; Thu, 10 Feb 2011 17:57:39 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 10 Feb 2011 17:57:52 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 10 Feb 2011 17:57:52 -0800
Received: from TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com ([169.254.5.102]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Thu, 10 Feb 2011 17:57:53 -0800
From: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
To: Greg Wilkins <gregw@webtide.com>, "Yutaka_Takeda@playstation.sony.com" <Yutaka_Takeda@playstation.sony.com>
Thread-Topic: [hybi] Final HTTP responses and WebSocket handshake
Thread-Index: AQHLyYwlLpFV95ISsE6ndh1yDTQPUZP8DqAA//97lpA=
Date: Fri, 11 Feb 2011 01:57:51 +0000
Message-ID: <CA566BAEAD6B3F4E8B5C5C4F61710C1126E085B9@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <OFDD4ABE05.D6C65821-ON88257833.00822B82-88257834.0009316B@playstation.sony.com> <AANLkTi=rFieVgfMaBn+pqp_M1bLdf0+Bm0NCApL+Rpih@mail.gmail.com>
In-Reply-To: <AANLkTi=rFieVgfMaBn+pqp_M1bLdf0+Bm0NCApL+Rpih@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Final HTTP responses and WebSocket handshake
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 01:57:40 -0000

This is not aligned with the WG consensus for HTTP compatibility (up until the websocket handshake is complete) declared some time back by the chairs.
The websocket handshake is not complete until a 101 comes back. So anything before than (including other response codes, reauthentication, etc) are not anything the websockets draft can say anything about. It's just compatible HTTP as usual.

So this is a bug in the spec, hopefully to get taken care of in 06.

> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
> Greg Wilkins
> Sent: 10 February, 2011 17:49
> To: Yutaka_Takeda@playstation.sony.com
> Cc: hybi@ietf.org
> Subject: Re: [hybi] Final HTTP responses and WebSocket handshake
> 
> On 11 February 2011 12:40,  <Yutaka_Takeda@playstation.sony.com> wrote:
> >
> > o  Cannot get full benefit out of HTTP protocol during the handshake
> > as it does not expect a final response:
> >   For example:
> >    - Can not redirect WebSocket handshake to another server (for load
> > balancing, fail-over, etc.)
> >    - Can not perform user authentication (Basic, Digest, etc.) during
> > the handshake.
> >    - Similarly, 407 authentication cannot be forced by the server.
> 
> +1
> 
> In the ancient history of this list, I have long argued for exactly this.
> 
> Apparently there are some security concerns about browser redirection, which
> I never really understood... and even if there are, I don't see the reason that the
> protocol should deny the use of non 101 handshake responses to all clients.  I
> think the protocol should allow arbitrary response codes (because it can't
> actually prevent them being sent by non WS servers anyway), and then
> individual clients can decide which responses they will handle (which may be
> better discuss in the appropriate HTML 5 forums regarding the specific
> websocket API).
> 
> cheers
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

v2.23.0 | Report a Bug | By Email