IETF Logo Mail Archive

Re: [hybi] #1: HTTP Compliance

Julian Reschke <julian.reschke@gmx.de> Mon, 17 May 2010 12:24 UTC

Return-Path: <julian.reschke@gmx.de>
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 B6B853A6AF9 for <hybi@core3.amsl.com>; Mon, 17 May 2010 05:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.787
X-Spam-Level:
X-Spam-Status: No, score=-2.787 tagged_above=-999 required=5 tests=[AWL=-2.788, BAYES_50=0.001]
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 DRElgyrO6yaf for <hybi@core3.amsl.com>; Mon, 17 May 2010 05:24:21 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 94FAD3A6B83 for <hybi@ietf.org>; Mon, 17 May 2010 05:13:00 -0700 (PDT)
Received: (qmail invoked by alias); 17 May 2010 12:12:50 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.116]) [217.91.35.233] by mail.gmx.net (mp053) with SMTP; 17 May 2010 14:12:50 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+NWlRzCYONQo2RuEONbGyMgOJynt09a7JZNjDk31 VKayjhT91Z64YO
Message-ID: <4BF132BA.10208@gmx.de>
Date: Mon, 17 May 2010 14:12:42 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: Greg Wilkins <gregw@webtide.com>
References: <068.d07026741c6694cd80652d2a7d34f236@tools.ietf.org> <4BF106AD.6020506@webtide.com> <Pine.LNX.4.64.1005170918310.25609@ps20323.dreamhostps.com> <4BF11920.2080307@webtide.com> <Pine.LNX.4.64.1005171039050.25609@ps20323.dreamhostps.com> <4BF12FF1.2020101@webtide.com>
In-Reply-To: <4BF12FF1.2020101@webtide.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "hybi@ietf.org" <hybi@ietf.org>
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:24:22 -0000

On 17.05.2010 14:00, Greg Wilkins wrote:
> ...
> Please try reading some of the many examples that I have sent in
> detail, but in summary:
>
>    + authentication cookie missing
>    + wrong URL given to the websocket client.
>    + poor deployment (with apache or similar in front or
>      in a server that does not support websocket).
>    + some other exception made the webapplication fail
>      to start, so the container sends a 503
>    + some exception in handling the request causes a 500
>    + some stupid caching proxy sends a 200 response
>
>
> Websocket clients are going to receive 404's, 503's etc.
> They are going to have to handle them sensibly and report
> reasonable errors to the user.
> ...

For the record: +1

Best regards, Julian

v2.37.1 | Report a Bug | By Email | System Status