Closed
Bug 667490
Opened 13 years ago
Closed 13 years ago
EventSource should use the same nsIContentPolicy type as XHR
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(2 files)
|
(deleted),
patch
|
dveditz
:
review+
|
Details | Diff | Splinter Review |
|
(deleted),
patch
|
Details | Diff | Splinter Review |
No description provided.
|
Assignee | |
Comment 2•13 years ago
|
||
This is what was discussed during security review.
Assignee: nobody → Olli.Pettay
Attachment #542793 -
Flags: review?(dveditz)
|
|
Assignee | |
Comment 3•13 years ago
|
||
We could also just add a new type for eventsource.
I don't know which one is better.
EventSource works in many ways like multipart XHR.
|
||
Comment 4•13 years ago
|
||
Comment on attachment 542793 [details] [diff] [review]
patch
r=dveditz
What type is websockets using? Should probably be the same. "XHR" == "script initiated data connection"? Could even add
const unsigned long TYPE_DATAREQUEST = 11;
to the IDL as an alias. Don't remove the existing one though: it's used by several add-ons.
Attachment #542793 -
Flags: review?(dveditz) → review+
Blocks: 692067
|
|
Assignee | |
Comment 5•13 years ago
|
||
|
|
Assignee | |
Comment 6•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Updated•12 years ago
|
Component: DOM: Other → DOM
|
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•