Re: [hybi] WS URLs

Tobias Oberstein <tobias.oberstein@tavendo.de> Mon, 24 October 2011 13:16 UTC

Return-Path: <tobias.oberstein@tavendo.de>
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 4011F21F8D80 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9nrS9CLygI2 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:16:38 -0700 (PDT)
Received: from EXHUB020-2.exch020.serverdata.net (exhub020-2.exch020.serverdata.net [206.225.164.29]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7E521F8D7E for <hybi@ietf.org>; Mon, 24 Oct 2011 06:16:38 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.230]) by EXHUB020-2.exch020.serverdata.net ([206.225.164.29]) with mapi; Mon, 24 Oct 2011 06:16:38 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Mon, 24 Oct 2011 06:16:36 -0700
Thread-Topic: [hybi] WS URLs
Thread-Index: AcySTTai31p+TV62S12LJI/WTtwtDgAAJVvg
Message-ID: <634914A010D0B943A035D226786325D42D0B036DC0@EXVMBX020-12.exch020.serverdata.net>
References: <AcyRAfMcynScsoopThG4iaBqB+cA5Q==> <634914A010D0B943A035D226786325D42D0B036D37@EXVMBX020-12.exch020.serverdata.net> <CADkeqZWDBH1KP2yLXSvNz+zyqGuWcwNBUzKgbupLCSZHsKXyTQ@mail.gmail.com>
In-Reply-To: <CADkeqZWDBH1KP2yLXSvNz+zyqGuWcwNBUzKgbupLCSZHsKXyTQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] WS URLs
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 24 Oct 2011 13:16:39 -0000

Hello Alexey,

> > 
> > Which of the following URLs are valid WS URLs?
> >
> > 1. ws://example.com/something#somewhere
> > 2. ws://example.com/something#somewhere/
> > 3. ws://example.com/something#somewhere/foo
> > 4. ws://example.com/something?query=foo#bar
> I think all of these are invalid. 

Ok.

> > When an invalid WS URLs is received in the client request during opening handshake,
> > how is the server supposed to react?
> As far as I remember WS/WSS URLs are not sent during the opening handshake. They can only be used to initiate one.

Sorry, what I meant with sending was not the complete WS URL, but the /resource/ component of the WS URL.

That is, what if a WS client starts the handshake with a

GET /something#somewhere/foo HTTP/1.1
Host: example.com
..

Now, what should the server do?

Go on with

/resource/ == "/something"

ignoring the fragment component, or fail the handshake with 400?