[network markers] Support all redirections in the parent process
Categories
(Core :: Networking: HTTP, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox92 | --- | fixed |
People
(Reporter: julienw, Assigned: julienw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file, 5 obsolete files)
Currently we're missing out a lot of redirections:
- STS
- proxy
- from addons
In this bug I want to experiment moving adding LOAD_REDIRECT markers directly in SetupReplacementChannel which is used in all redirections.
I'll probably also reuse asuth's code from https://phabricator.services.mozilla.com/D112675, because after having a redirect marker when redirecting to InterceptedChannel we also need a new id and a new "start" marker.
This may not be the best solution for the end users, but we may want to hide or merge internal redirections in the UI later on.
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
This moves the adding of the end marker for redirects in nsHttpChannel
to SetupReplacementChannel, so that all redirects are properly caught.
Without that, some requests will show as unfinished in the profiler
frontend.
Some of the redirects are internal and we may be able to flag and ignore
them in the frontend, but that's work for the future.
Assignee | ||
Comment 2•4 years ago
|
||
This ensures that the new intercepted channel gets a new id, so that we
can properly match start and end markers in the frontend.
Depends on D118823
Assignee | ||
Comment 3•4 years ago
|
||
Following the change in the previous commit where we generate a new id
for intercepted channels, we now need a "start" marker for this channel.
Depends on D118824
Assignee | ||
Comment 4•4 years ago
|
||
Now we need to update all existing tests related to service workers,
because they all have an extra redirect marker.
Depends on D118825
Assignee | ||
Comment 5•4 years ago
|
||
This adds a new profiler test for handling the http->https case that we
wouldn't catch before this patchset.
Depends on D118826
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 7•4 years ago
|
||
This moves the adding of the end marker for redirects in nsHttpChannel
to SetupReplacementChannel, so that all redirects are properly caught.
Without that, some requests will show as unfinished in the profiler
frontend.
Some of the redirects are internal and we may be able to flag and ignore
them in the frontend, but that's work for the future.
Because all redirections get a "REDIRECT" end marker, including the
internal redirection to the service worker's intercepted channel, we now
need an additional "START" marker there as well.
All existing profiler tests related to service workers needed to be
updated because there's an extra redirect marker in all these requests,
as well as several pairs of markers that all have the same id.
This also adds a new profiler test for handling the http->https case
that we wouldn't catch before this patch.
![]() |
||
Comment 9•4 years ago
|
||
bugherder |
Comment 10•4 years ago
|
||
Backed out for causing bug 1719684
Backout link: https://hg.mozilla.org/integration/autoland/rev/94d7910fbb31106daa0395424d67211b7c806e69
Updated•4 years ago
|
![]() |
||
Comment 12•4 years ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/94d7910fbb31106daa0395424d67211b7c806e69
Comment 13•4 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:julienw, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 14•4 years ago
|
||
![]() |
||
Comment 15•4 years ago
|
||
bugherder |
Description
•