W3C home > Mailing lists > Public > public-webappsec@w3.org > February 2014

Re: Remove paths from CSP?

From: Mike West <mkwst@google.com>
Date: Wed, 12 Feb 2014 09:52:36 +0100
Message-ID: <CAKXHy=emPBuwCMtFz9uk-DyL8hs4oDYiVdujuDRYQbhMi6yQyg@mail.gmail.com>
To: "Eduardo' Vela" <evn@google.com>
Cc: Daniel Veditz <dveditz@mozilla.com>, Garrett Robinson <grobinson@mozilla.com>, Brad Hill <bhill@paypal-inc.com>, Michal Zalewski <lcamtuf@google.com>, Odin Hørthe Omdal <odinho@opera.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>, Adam Barth <w3c@adambarth.com>
On Wed, Feb 12, 2014 at 9:33 AM, Eduardo' Vela" <Nava> <evn@google.com>wrote:

> Well, we won't be able to use CSP in Google since we (unfortunately) serve
> static JS APIs from www.google.com (which also has a lot of JSONP-like
> endpoints).
> These are also public APIs, so our users of such APIs won't be able to
> adopt CSP either.
I don't understand why a lack of paths in source expressions would mean
that Google can't adopt CSP. Users would whitelist 'www.google.com' (or '
developers.google.com') as a valid source of script. It wouldn't be as
narrow or lovely as 'developers.google.com/loader', but it's certainly not

Can you explain?

Received on Wednesday, 12 February 2014 08:53:36 UTC

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