Open
Bug 1187328
Opened 10 years ago
Updated 2 years ago
service workers should not be able to make http requests when there is no browsing context
Categories
(Core :: DOM: Service Workers, defect, P3)
Core
DOM: Service Workers
Tracking
()
NEW
People
(Reporter: bkelly, Unassigned)
References
(Blocks 1 open bug)
Details
This is a consequence of mixed content and its integration with SW. See:
https://github.com/whatwg/fetch/issues/69
Comment 1•9 years ago
|
||
Ehsan wonders if this is true for Shared Workers as well.
Flags: needinfo?(bkelly)
Reporter | ||
Comment 2•9 years ago
|
||
I don't think SharedWorkers can exist without a document attached, can they? I thought the SharedWorker was stopped when the last document closed.
Flags: needinfo?(bkelly)
Comment 3•9 years ago
|
||
They can exist with more than one Client...
Comment 4•9 years ago
|
||
Note: request window is defined here: <https://fetch.spec.whatwg.org/#concept-request-window>
Updated•9 years ago
|
Assignee: nobody → ehsan
Updated•9 years ago
|
Status: NEW → ASSIGNED
Updated•9 years ago
|
Reporter | ||
Comment 5•9 years ago
|
||
We don't think this blocks v1 because currently the only way to get a service worker without a window is via a push event, which is separate from v1.
Also, I think the spec has changed a bit here. It now has the concept of the associated window as an internal property on the Request. This would likely be reflected in our code by stashing the intercepted channel's loading document on InternalRequest and then using it for the FetchDriver channel.
Reporter | ||
Updated•8 years ago
|
Assignee: ehsan → nobody
Status: ASSIGNED → NEW
Summary: Test the service workers cannot make http requests when there is no browsing context → service workers should not be able to make http requests when there is no browsing context
Updated•7 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•