Re: [hybi] WebSocket Subprotocol Close Code: Bad Gateway

Johan de Vries <devries@wivion.nl> Thu, 15 September 2016 06:27 UTC

Return-Path: <devries@ixon.co>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC7A12B0D8 for <hybi@ietfa.amsl.com>; Wed, 14 Sep 2016 23:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wivion.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTQIn021DgnF for <hybi@ietfa.amsl.com>; Wed, 14 Sep 2016 23:27:20 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 872CE12B0E3 for <hybi@ietf.org>; Wed, 14 Sep 2016 23:27:20 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id n143so60394003ita.1 for <hybi@ietf.org>; Wed, 14 Sep 2016 23:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wivion.nl; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WpQrxGfYcGOsqZTq/hkK/YCDeieEwT5xczSM1nYI5y4=; b=S2MDDPoiH+esCOdik1hVFXC5RvTInCzKNzZ7KXubjwEuXtK9D/5edyNK7DcMNKUqfv vvZ6wpkjjlEmNLASDCj8ID4V4FGPQmhwWCX39VoE31e3EO6RB0uriD0xlLAztlZBzqmg u93Uk/PIt8heeM8J80weddXJL3Tlx68cO0qyQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WpQrxGfYcGOsqZTq/hkK/YCDeieEwT5xczSM1nYI5y4=; b=PVOSPYU9kFLvs3vYtVAbQCDioTJKf0CIPG7pNkquimeo2PBNfgwrIikVzfPt1pktY5 PuNWZun3JwOOVsW3O1vFyaSAF3BMb2UWb4b1xUaGCD4M4dZuY8NG75/lDMjZwK/d5Lwq cg9JW5koKFy7VLCF4p80VjOM+mFQMPiE+BFSYeep5fjq0XiLCWzN6RbpiCYIOiELzt09 FGGSFHo9p3CiL0+zqcEr5zGu6/9ti5Aa0246iWmafwkBwHg2bXt16ZKoc6CZ6ldwwHuE +I0jWOqwav8yaJxdXTRoy62zJFGlnu3lvTYZeYycYkUiNa/kXiHrzj+3p2206m+YvTQb bsEg==
X-Gm-Message-State: AE9vXwNBVe/T57ezju6xAyLQs7IQCfXOIx8cJUeDNsluRMjDGOtBd6A6zeGX5P0FHHh9yHUTSNgESTpymKljWw==
X-Received: by 10.107.58.7 with SMTP id h7mr5779804ioa.141.1473920839640; Wed, 14 Sep 2016 23:27:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.4.15 with HTTP; Wed, 14 Sep 2016 23:27:18 -0700 (PDT)
In-Reply-To: <CAHixhFr6DqiFnRLEV=4_jZiJcLm1rgVdxFTW4hQqB+OsXDNPUg@mail.gmail.com>
References: <CA+Y8h61FxUDgiPmgLwqy9qqzLYGWhvsg9bjMR3PXPtf5qj2VLA@mail.gmail.com> <CAHixhFr6DqiFnRLEV=4_jZiJcLm1rgVdxFTW4hQqB+OsXDNPUg@mail.gmail.com>
From: Johan de Vries <devries@wivion.nl>
Date: Thu, 15 Sep 2016 08:27:18 +0200
Message-ID: <CA+Y8h60C2rtk4hogYAU4JfSbsXoMfV+r+6HWNS=tgNPSLm5ODw@mail.gmail.com>
To: Adam Rice <ricea@google.com>
Content-Type: multipart/alternative; boundary="001a114abfba12fbee053c85f00f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/AoijY6ndcVdF0K5o4CkVRljTBrE>
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] WebSocket Subprotocol Close Code: Bad Gateway
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 15 Sep 2016 06:27:23 -0000

I'm sorry, maybe I misunderstood.

In the provided links I couldn't find anything about how to request such a
reservation, except this mailing list. Is this not the right place to
request it?

Met vriendelijke groet,

Johan de Vries

Wivion bv
Vierlingsbeekseweg 52A | NL-5825 AX  Overloon
www.wivion.nl

2016-09-12 13:13 GMT+02:00 Adam Rice <ricea@google.com>:

> I can see how that might be useful.
>
> RFC 6455 section 11.7 provides for adding new status codes. See
> https://tools.ietf.org/html/rfc6455#section-11.7 and http://www.iana.org/
> assignments/websocket/websocket.xhtml#close-code-number
>
> On 8 September 2016 at 23:53, Johan de Vries <devries@wivion.nl> wrote:
>
>> Hello,
>>
>>
>> I would like to reserve a status code much akin to HTTP's 502 Bad Gateway.
>>
>> The description would be the same as for 502: The server was acting as a
>> gateway or proxy and received an invalid response from the upstream server.
>>
>> My motivation is that I'm implementing an application that allows a
>> website to connect to a server over WebSockets (much like Guacamole does).
>> It would be useful to be able to indicate when a proxy error occurs to the
>> client.
>>
>> I'm not sure what range this should be in, so I'm not claiming a number.
>> I think it's generic enough to warrant the next number in the list (1016?)
>> but again I'm not sure about how this part works.
>>
>>
>> Met vriendelijke groet,
>>
>> Johan de Vries
>>
>> Wivion bv
>> Vierlingsbeekseweg 52A | NL-5825 AX  Overloon
>> www.wivion.nl
>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>>
>>
>