service worker: Do allowed origin check on StartWorker.
We were only doing this check at registration time previously, which is sketchy since the browser or content settings could change in the meantime after registration. Actually the motivating example was if you register an extension service worker once and then run Chrome with --disable-extensions and then try to start the worker via chrome://serviceworker-internals. It turns out the checks for JavaScript and cookies in ChromeContentBrowserClient::AllowServiceWorker were disallowing start worker in that case, but it seems fragile to rely on those. Change-Id: Iea3706ccf08ec72ed9e2306b01a6ddfd0fa3b9eb Reviewed-on: https://chromium-review.googlesource.com/1027171Reviewed-by:Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#553483}
Showing
This diff is collapsed.
Please register or sign in to comment