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

[suborigins] Accessing workers from suborigins

From: Mitar <mmitar@gmail.com>
Date: Wed, 3 Feb 2016 12:14:05 -0800
Message-ID: <CAKLmikPw+AQ=0OzUpaAyAUV3SdFLR+-LUYmc453ZoG+9Hm-Fig@mail.gmail.com>
To: "public-webappsec@w3.org" <public-webappsec@w3.org>
Hi!

So, based on the current draft (29 January 2016), web workers should
work from suborigins, but currently this is not yet implemented in
Chrome (https://code.google.com/p/chromium/issues/detail?id=580320).
So this is just not yet implemented? Because I saw some tests which
test that you cannot create a web worker at all when suborigin is in
effect? Is this just temporary?

I would also pitch in against the current text about service workers, this part:

> As a result of the above restriction on Workers, since a Service Worker cannot be created by a Suborigin, no Service Workers will be able to intercept the requests of a Suborigin.

Please do not prevent this. We currently use service worker to
intercept requests from suborigins and then based on a suborigin
decide what to do, which resources to serve and how. As currently
implemented in Chrome this works well, so no need to remove/prevent
it. :-)


Mitar

-- 
http://mitar.tnode.com/
https://twitter.com/mitar_m
Received on Wednesday, 3 February 2016 20:14:37 UTC

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