Open Bug 1697204 Opened 4 years ago Updated 3 years ago

When there's a "fake" redirection because of a URL mismatch in a serviceworker answer, we should indicate it in the network marker payload

Categories

(Core :: Gecko Profiler, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: julienw, Unassigned)

References

(Blocks 1 open bug)

Details

STR:

  1. Open profiler.firefox.com, wait a few seconds until the service worker is installed (this is visible in the web console).
  2. start a profile.
  3. reload the page
  4. Capture the profile
  5. Open the network chart for the thread with some network markers.

=> Notice that most network markers are duplicated, one is "redirected" and the other one has a parameter __uncache. The latter is the cached Response from when the service worker was installed, an internal redirect was done.

We should either hide this redirect and make it clear the answer comes from the service worker with a different URL, or indicate clearly why a redirect is done.

Severity: -- → N/A
Priority: -- → P3

Now we display in the tooltip that the redirection is internal, but this is still awkward => https://share.firefox.dev/378SThP
Currently both requests start at the same location, probably we should make the second one start at the end of the first, so that in the frontend we can more easily make both on the same line.

You need to log in before you can comment on or make changes to this bug.