- From: Maciej Stachowiak <mjs@apple.com>
- Date: Wed, 20 Apr 2011 02:57:32 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Adam Barth <ietf@adambarth.com>, "public-iri@w3.org" <public-iri@w3.org>
I have personally seen a serious security bug from incorrect handling of location.path (though I am not free to disclose the details). So yes, this stuff matters, in general. Regards, Maciej On Apr 19, 2011, at 11:31 PM, Julian Reschke <julian.reschke@gmx.de> wrote: > On 20.04.2011 08:22, Adam Barth wrote: >> ... >> It's a moderate problem in practice. For example, every browser I'm >> aware of has had (historically) security bugs arising from subtly >> different URL processing by various components. We also have examples >> of compatibility problems with web sites arising from different URL >> processing by browsers. >> ... > > Yes. Sure. > > My question was: do the differences in the behavior of the decomposition attributes cause problems in practice? What type of code is using them? (I really want to know :-). > > I think it would be great if one result of this WG's activity would be the definition of a standard JS API for processing URIs/IRIs/references in browsers. > > Best regards, Julian
Received on Wednesday, 20 April 2011 09:58:09 UTC