W3C home > Mailing lists > Public > public-webappsec@w3.org > January 2015

Re: [Integrity] typos with ni URIs

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 20 Jan 2015 19:05:23 +0100
Message-ID: <CADnb78gcQ4eGD0X9iKKt5qqAxprGNzppEBtWtzcSxWvNVNqTuA@mail.gmail.com>
To: Brad Hill <hillbrad@gmail.com>
Cc: Brian Smith <brian@briansmith.org>, Martin Thomson <martin.thomson@gmail.com>, Mike West <mkwst@google.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>, "Manger, James" <James.H.Manger@team.telstra.com>
On Tue, Jan 20, 2015 at 6:51 PM, Brad Hill <hillbrad@gmail.com> wrote:
> "not invented here".

That seems unfair. As far as I know we don't currently use URLs for
anything other than fetching and navigating throughout the web
platform. We do have a fair amount of trivial microsyntaxes for other
tasks, especially in HTML.

It is also not like we get any leverage out of using URLs here as this
is essentially a microsyntax layered on top of a URL. We first have to
parse it as a URL, then I guess we have to check that there is no host
component (not possible per current URL parser definition by the way),
then we have to split the path component in various ways and do checks
on the query. Did you define processing for what happens if there is a
fragment there or username and password information?

Received on Tuesday, 20 January 2015 18:05:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:44 UTC