Re: [hybi] WS URLs

Julian Reschke <julian.reschke@gmx.de> Mon, 24 October 2011 13:28 UTC

Return-Path: <julian.reschke@gmx.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 A22DC21F8C60 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.969
X-Spam-Level:
X-Spam-Status: No, score=-102.969 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hNAKyriMYYGG for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:28:30 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id E9E2A21F8C22 for <hybi@ietf.org>; Mon, 24 Oct 2011 06:28:22 -0700 (PDT)
Received: (qmail invoked by alias); 24 Oct 2011 13:28:21 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp059) with SMTP; 24 Oct 2011 15:28:21 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/vHIVpGJTv/FA2x15L0aUQlNE3bT+C3UK/Ww7cQK NNq1f8tPVSdSyP
Message-ID: <4EA567F1.4050702@gmx.de>
Date: Mon, 24 Oct 2011 15:28:17 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
References: <AcyRAfMcynScsoopThG4iaBqB+cA5Q==> <634914A010D0B943A035D226786325D42D0B036D37@EXVMBX020-12.exch020.serverdata.net> <CADkeqZWDBH1KP2yLXSvNz+zyqGuWcwNBUzKgbupLCSZHsKXyTQ@mail.gmail.com> <634914A010D0B943A035D226786325D42D0B036DC0@EXVMBX020-12.exch020.serverdata.net>
In-Reply-To: <634914A010D0B943A035D226786325D42D0B036DC0@EXVMBX020-12.exch020.serverdata.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 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:28:31 -0000

On 2011-10-24 15:16, Tobias Oberstein wrote:
> 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?
 > ...

That's an HTTP question; as the

   /something#somewhere/foo

is not a valid rquest-target according to 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-latest.html#request-target>, 
the server should reject the request with a 400 status.

Best regards, Julian