Re: [xmpp] See-other-uri and insecure web sockets

Ben Campbell <ben@nostrum.com> Wed, 05 March 2014 09:34 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716441A000D for <xmpp@ietfa.amsl.com>; Wed, 5 Mar 2014 01:34:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 SAG2qpBszoNM for <xmpp@ietfa.amsl.com>; Wed, 5 Mar 2014 01:34:05 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2ED1A00F2 for <xmpp@ietf.org>; Wed, 5 Mar 2014 01:30:14 -0800 (PST)
Received: from dhcp-bfe5.meeting.ietf.org (dhcp-bfe5.meeting.ietf.org [31.133.191.229]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s259TtLH090836 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Mar 2014 03:29:58 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <53168116.7080107@stpeter.im>
Date: Wed, 5 Mar 2014 09:29:55 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <999EB1E4-DC95-4343-AD1C-6606447755D2@nostrum.com>
References: <E72F7F55-02DE-449E-A68C-BA8B18DAE975@vidyo.com> <CAOb_Fnzw_dw3V5W2U5M6ch2k5d=HmpUdjBYbJJQSpkWKH=V+1w@mail.gmail.com> <C3B7485D-C58A-40C9-90EE-7A18B688CBBC@vidyo.com> <53168116.7080107@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/oPifSPWP7YYkU8J1Rn_L9KhniqE
Cc: Jonathan Lennox <jonathan@vidyo.com>, "xmpp@ietf.org" <xmpp@ietf.org>
Subject: Re: [xmpp] See-other-uri and insecure web sockets
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2014 09:34:06 -0000

On Mar 5, 2014, at 1:42 AM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

>> 
>> Well, you need to do *something* if someone tries to connect to <ws://websocketserver.example/xmpp-bind>, but I guess responding with 301 or 404 to the HTTP handshake, prior to protocol handover, would be better than switching to xmpp and then using see-other-uri.
> 
> Yes, I think that's the better approach - the earlier the better.

Does that mean we don't need see-other-uri at all?