[hybi] WebSocket Subprotocol Close Code: Bad Gateway

Johan de Vries <devries@wivion.nl> Thu, 08 September 2016 14:53 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 AAE6B12B1CC for <hybi@ietfa.amsl.com>; Thu, 8 Sep 2016 07:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 ULcNNL7Mg1qX for <hybi@ietfa.amsl.com>; Thu, 8 Sep 2016 07:53:07 -0700 (PDT)
Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::235]) (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 196DC12B1C4 for <hybi@ietf.org>; Thu, 8 Sep 2016 07:53:06 -0700 (PDT)
Received: by mail-ua0-x235.google.com with SMTP id 95so18338025uaz.2 for <hybi@ietf.org>; Thu, 08 Sep 2016 07:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wivion.nl; s=google; h=mime-version:from:date:message-id:subject:to; bh=SaAHv4zshl0AmxKltbLfLoaK2G6jpX4b85k86gbFpP0=; b=KbtB2chtzovpm87/L4SEw4CqiEVP2YjqIotM3qgdSdwDtGS5Gcw89250NnC5XEnUsW GBjxanx/kIY0spikacu4z1iZy2nICek/SUN9ar+LVJpyKd1dNvJxhTCvEZCo3TKHQH3x nd79ngVHG4KESNs2SKElWs9nkyuf9pO8Ybsdg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=SaAHv4zshl0AmxKltbLfLoaK2G6jpX4b85k86gbFpP0=; b=dhpsLrwB9eF92oKlmmCjDcmbGhGvD4YaefFCS4EGEKBD1937aZToAv6mbC9k3VTo6y xB2m2z+UrkaawOnISsyLAWR6t/6M0wvIyGJdRgDSNAvf/rrj4rPlwxQyqrAWLpDPrxbw 6L8u3ndAKrYYQAXY5rH64rUo+DIc1BCOolqr7R9CE220r651G5gukYwyOG6zngg6T+GE PKBuTQJN+2lYYpQlzXqsKIggGmHpI8bFPFFxO1myZedH41VSIL0hH4lolDXiDlaRF/ZC k2aJEnkyZ3VRBAOTfESPEbGdn0zyr23/vPVNAwHCXnI5zriDeA5HhWiMFv932xQlSaC4 zCSQ==
X-Gm-Message-State: AE9vXwMX/wRHB4bFbOmwbyd/1kiSSY15zrXa6Y8QOh7OTxiPCo/UMzanbG3kvicJ0jNzMl7iHrD2OYltqGzEyQ==
X-Received: by 10.176.64.138 with SMTP id i10mr39863uad.82.1473346385786; Thu, 08 Sep 2016 07:53:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.206.2 with HTTP; Thu, 8 Sep 2016 07:53:05 -0700 (PDT)
From: Johan de Vries <devries@wivion.nl>
Date: Thu, 8 Sep 2016 16:53:05 +0200
Message-ID: <CA+Y8h61FxUDgiPmgLwqy9qqzLYGWhvsg9bjMR3PXPtf5qj2VLA@mail.gmail.com>
To: hybi@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c122e2cf4d0d9053c002f56
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/VOLI2xp4tzFnIFYespe6oOtpFXA>
Subject: [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, 08 Sep 2016 14:57:32 -0000

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