You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fetch says that a fetch request for a blob: URI inherits HTTPS state from the 'client', which means for blobs it inherits it from itself, which doesn't make much sense.
@mikewest what do you think the best thing to do is here? In a way we could just copy HTTPS state from whatever created the worker, since it'll be same-origin, but that doesn't really seem great or future proof.
HTTP state (and active CSP) seems like something that is tied to the place where the blob is created. I think we ought to be storing a few bits of information on the blob when it's created, and persist those through whenever it's instantiated/requested.
It seems that a Worker's 'client' is its own environment settings object.
https://html.spec.whatwg.org/#fetch-a-classic-worker-script
Fetch says that a fetch request for a blob: URI inherits HTTPS state from the 'client', which means for blobs it inherits it from itself, which doesn't make much sense.
https://fetch.spec.whatwg.org/#basic-fetch
The text was updated successfully, but these errors were encountered: