Closed
Bug 1476978
Opened 7 years ago
Closed 6 years ago
Provide APIs for Necko to perform redirection of top-level loads to a new process
Categories
(Core :: DOM: Navigation, enhancement)
Core
DOM: Navigation
Tracking
()
RESOLVED
DUPLICATE
of bug 1476996
Tracking | Status | |
---|---|---|
firefox63 | --- | affected |
People
(Reporter: mayhemer, Assigned: nika)
References
()
Details
According the agreed design we need two functions to be called by channels on the parent process:
1. (in case the load has not been redirected) determination if consummation of the response should happen in a new process
2. redirection of the response to a new process with passing down the following data:
- originalURL (first URL of the redirect chain)
- targetURL (the URL to create the channel with, the one we actually navigate to)
- resultPrincipalURL (null, or a URL to set on the channel's load info as the principal URL)
- probably load flags of the channel
- redirect ID (uint64_t that must be set on the loading channel before opening via nsIChildInterface)
The second function will start the whole process of finding or creating the new process and passing the necessary arguments to docshell to setup the channel and then open it.
![]() |
Reporter | |
Comment 1•7 years ago
|
||
Note that HttpChannelChild::SetupRedirect may be a good example of what all we may need to carry to the new channel... not a small amount.
Assignee | ||
Comment 2•7 years ago
|
||
I'm not sure why I am marked as the assignee on this bug - I was imagining that necko would implement a no-op version of the interface which we could replace once it had been implemented and tested :-).
Flags: needinfo?(valentin.gosu)
Comment 3•6 years ago
|
||
We handle all this in bug 1476996.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(valentin.gosu)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•