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

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 15 September 2016 08:36 UTC

Return-Path: <alexey.melnikov@isode.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 2DECA12B186 for <hybi@ietfa.amsl.com>; Thu, 15 Sep 2016 01:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.507
X-Spam-Level:
X-Spam-Status: No, score=-3.507 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, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 0EAjC4yB1PG5 for <hybi@ietfa.amsl.com>; Thu, 15 Sep 2016 01:36:17 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 3A62B12B03D for <hybi@ietf.org>; Thu, 15 Sep 2016 01:36:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1473928576; d=isode.com; s=june2016; i=@isode.com; bh=+AWdEwFELZotHRrFjfHC02NUeLgH2sG7swIv7DCdNk0=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=eU3+lNNsC3SSA5IWKk7fnnKUKw6CXZFqwIeeOijk1VRmVOG2HLwHqkJdZGU2L5Wf495CkY pJAAzBv6uelCyMYEegG5kVe5EyW6kkls8wHPosL7NIT6rOPWkDNONJ7PYYf6w8Rgek9Jkf MY7vmkU+xaTzLAqNDm5KbPn466RdvtU=;
Received: from [192.168.10.56] ((unknown) [87.193.150.154]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <V9pdfwBM5UcY@waldorf.isode.com>; Thu, 15 Sep 2016 09:36:16 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (13G36)
In-Reply-To: <CAHixhFrMj4BVGAXgsfQp-gALfD-m=4NyUuUCPDk+5OHcPyxhQg@mail.gmail.com>
Date: Thu, 15 Sep 2016 10:49:05 +0200
Message-Id: <332C4AF9-ED0E-43D0-B606-0BD3DAA6D2EF@isode.com>
References: <CA+Y8h61FxUDgiPmgLwqy9qqzLYGWhvsg9bjMR3PXPtf5qj2VLA@mail.gmail.com> <CAHixhFr6DqiFnRLEV=4_jZiJcLm1rgVdxFTW4hQqB+OsXDNPUg@mail.gmail.com> <CA+Y8h60C2rtk4hogYAU4JfSbsXoMfV+r+6HWNS=tgNPSLm5ODw@mail.gmail.com> <CAHixhFrMj4BVGAXgsfQp-gALfD-m=4NyUuUCPDk+5OHcPyxhQg@mail.gmail.com>
To: Adam Rice <ricea@google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="Apple-Mail-6CAFE384-4EF1-48FE-9D57-0E6A2220FBF7"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/2G2B2mULkoabI0uf7iIBuK6WXg0>
Cc: "hybi@ietf.org" <hybi@ietf.org>, Johan de Vries <devries@wivion.nl>
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 08:36:19 -0000

Hi,

> On 15 Sep 2016, at 09:54, Adam Rice <ricea@google.com> wrote:
> 
> I think this list is the right place, but since the working group has closed you may have trouble attracting enough discussion to have consensus.
> 
> This appears to be the link from the last time it happened: http://www.ietf.org/mail-archive/web/hybi/current/msg09670.html

I am the designated expert for this registry:
http://www.iana.org/assignments/websocket/websocket.xhtml#close-code-number

So I will help with getting this registered. But this might take a few days, currently travelling.

> 
>> On 15 September 2016 at 15:27, Johan de Vries <devries@wivion.nl> wrote:
>> 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
> 
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi