Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workers with blob: URIs should inherit HTTPS state #929

Closed
jwatt opened this issue Mar 23, 2016 · 4 comments · Fixed by #5784
Closed

Workers with blob: URIs should inherit HTTPS state #929

jwatt opened this issue Mar 23, 2016 · 4 comments · Fixed by #5784
Assignees

Comments

@jwatt
Copy link

jwatt commented Mar 23, 2016

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

@annevk
Copy link
Member

annevk commented Apr 4, 2016

@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.

@mikewest
Copy link
Member

mikewest commented Apr 4, 2016

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.

@annevk
Copy link
Member

annevk commented Apr 4, 2016

That makes sense.

@annevk
Copy link
Member

annevk commented Apr 4, 2016

I think that makes this a bug of File API and Fetch. @jwatt agreed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants