Re: URL parsing in HTML5 from Elisabeth Robson on 2011-11-04 (public-html-comments@w3.org from November 2011)

From: Elisabeth Robson <bethrobson@gmail.com>
Date: Fri, 4 Nov 2011 08:59:01 -0700
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Anne van Kesteren <annevk@opera.com>, "public-iri@w3.org" <public-iri@w3.org>, public-html-comments@w3.org, Peter Saint-Andre <stpeter@stpeter.im>, Sam Ruby <rubys@intertwingly.net>, "Paul Cotton (pcotton@microsoft.com)" <pcotton@microsoft.com>, Ian Hickson <ian@hixie.ch>, "Michael(tm) Smith" <mike@w3.org>, Adam Barth <ietf@adambarth.com>, "Edward O'Connor" <ted@oconnor.cx>
Message-ID: <CAFSNtX5ZKGdehAddF8HdhDkH3-aT0dk9EYox=RL6Kot=HAhKDg@mail.gmail.com>

Sorry, joining the conversation a bit late, can you explain more
specifically what you mean by URIs "leaking" in this context?

Thanks

On Fri, Nov 4, 2011 at 8:50 AM, Julian Reschke <julian.reschke@gmx.de>wrote:

>
> I do agree that URIs leak, but that doesn't necessarily mean that we can
> have the same processing requirements everywhere. For instance, there are
> cases where whitespace acts as a delimiter and thus will not be accepted as
> URI character, no matter how much you want it to.
>
>

Received on Friday, 4 November 2011 17:49:20 UTC