IETF Logo Mail Archive

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

Adam Rice <ricea@google.com> Mon, 12 September 2016 11:13 UTC

Return-Path: <ricea@google.com>
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 1A6D112B20C for <hybi@ietfa.amsl.com>; Mon, 12 Sep 2016 04:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 IyQ1GPX5Rvvi for <hybi@ietfa.amsl.com>; Mon, 12 Sep 2016 04:13:30 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (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 BEB9812B208 for <hybi@ietf.org>; Mon, 12 Sep 2016 04:13:30 -0700 (PDT)
Received: by mail-vk0-x22b.google.com with SMTP id m62so74259917vkd.3 for <hybi@ietf.org>; Mon, 12 Sep 2016 04:13:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pJKxyZ3d+ytSoshME/j0MM34eL5IHVsoStTYPgcd2VE=; b=Y2DoESFYGbIEy8MUHbrGxrozWGhsLywm8t/TrAch2cnvGMYhjUn2eIxf91Wj/0jpgd KfPZbrrTcl+TioQeSkqa4gvlluhWF2EkHRSmOJMJK8KuaLg118CwF49Z/ohbzrF8kUuo vTsbAVvGGK6Kz7e4ciHSG6odJ5EieFDnvRJGfqzcuWnVe19MhEU2PuwEEcv36l8S+S8Q X5dyD9iQp7IZcpJV0WKItZgfFhMSwDCL3LYiCnNPcWDwjP9UylGxlCaaoOnVVFfHdesV TAzVuL/HOU3PavpmulBATYJzg7nuIuYBnW2NkVsG6k8FtUr0Nzd51j1m1v0MZWXE0DtQ iSzw==
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=pJKxyZ3d+ytSoshME/j0MM34eL5IHVsoStTYPgcd2VE=; b=Lu2k8pHjdeNktjmfKWg3ysULlKcnKbcdHYWh6WyEkcM+g6B+Mtzr6Ha4Wfyyl49L2W SnEP/Lm+nj7jRleqnnEhxwRWnnNRQjH8i9HMJOmYl2dQ6EK5+Iflu9HkI7gC0IN+5KKL C04o/sh4wYf0gAjonEKXZ3ib66Y707e32DxZXCExt8GV+MvYE052FoNUjPGv2u5wZSZ9 q+y1pTxEd5bC9/xehLANK4M0g1udshF2l2rDSepri5Dr6uDltIvkJuIfxQ3PB5+vWytC igwMMmG6USnHOYHFWhJlSlULTnsdB3uc14K/mBXxWlOG2pZgXULD94BvcHBH+16PYYJI /HXA==
X-Gm-Message-State: AE9vXwNKYdqYtkWcmnq9NQjeqbn7DfoOlF+TvoDJG3iB7Co0cxi4rFjyeXmsRj5hSNGopmGsmBRrX7hyMFyPsex+
X-Received: by 10.31.229.193 with SMTP id c184mr11185329vkh.134.1473678809687; Mon, 12 Sep 2016 04:13:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.157.135 with HTTP; Mon, 12 Sep 2016 04:13:28 -0700 (PDT)
In-Reply-To: <CA+Y8h61FxUDgiPmgLwqy9qqzLYGWhvsg9bjMR3PXPtf5qj2VLA@mail.gmail.com>
References: <CA+Y8h61FxUDgiPmgLwqy9qqzLYGWhvsg9bjMR3PXPtf5qj2VLA@mail.gmail.com>
From: Adam Rice <ricea@google.com>
Date: Mon, 12 Sep 2016 20:13:28 +0900
Message-ID: <CAHixhFr6DqiFnRLEV=4_jZiJcLm1rgVdxFTW4hQqB+OsXDNPUg@mail.gmail.com>
To: Johan de Vries <devries@wivion.nl>
Content-Type: multipart/alternative; boundary="001a114dfa6cf74039053c4d95a2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/FY4DL80qphJIJ5MNbCwMPD4Pa1o>
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: Mon, 12 Sep 2016 11:13:32 -0000

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
>
>

v2.23.0 | Report a Bug | By Email