Some of requests in Network lack info
Categories
(DevTools :: about:debugging, defect, P3)
Tracking
(Not tracked)
People
(Reporter: owlish, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(2 files)
STR:
- Have an Android device with USB debugging enabled in Dev Settings and in Fenix.
- Run Fenix. Connect it to your computer via USB.
- On your computer, open either FF Nightly (80a1) or release FF (78.0.1). Go to
about:debugging
, connect to your device and open up the Fenix. - In FF Nightly, inspect Multiprocess Toolbox, on FF inspect Main Process.
- Go to Network tab.
- In Fenix, open a private tab and go to https://drive.google.com/file/d/1FNmuJkUivTWbihkjepp6zEwKtE6JGfjU/view?usp=drivesdk then click Download.
- Observe Download Failed on Fenix
- Look at the Network tab and observe the last three requests.
Expected behavior:
You are able to see the information on those three requests (headers, cookies, etc)
Actual behavior:
There's no information about the requests - no headers or cookies.
All of this happened on OS X 14.6 Mojave, the above versions of FF, and latest Fenix Nightly.
Please see the screenshot of what I see attached. I also saved the HAR with the requests in question - I had to use Google HAR analyzer to get the information on the requests. So it seems like the info is there, but it's not shown for some reason. Of course, I am not able to modify and resend the requests, which makes it hard to debug the Fenix/GeckoView issue I'm dealing with.
Reporter | ||
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
Thanks for filing.
It seems that the netmonitor only receives an initial information about the request creation, but never receives any update.
With the current implementation, this means we get information about the request in onNetworkResourceAvailable
firefox-data-provider.js#328, but never in onNetworkResourceUpdated.
Honza, are there known issues where the netmonitor will only show incomplete request information because we don't receive any update after the request creation?
Note that the console can show more information if you:
- start the toolbox without opening the console
- try to download
- switch to the console
In this case after enabling XHR logs in the console, we can see that the request failed with a 403 forbidden status code (however expanding the request in the console still only shows empty panels).
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #2)
- start the toolbox without opening the console
How do I do that?
Comment 4•5 years ago
|
||
(In reply to [:owlish] 🦉 PST from comment #3)
(In reply to Julian Descottes [:jdescottes] from comment #2)
- start the toolbox without opening the console
How do I do that?
The toolbox opens by default on the last tool you had selected.
So open the toolbox, select netmonitor, close the toolbox, open it again.
The toolbox will open on the netmonitor, and behind the scenes the console UI won't be initialized.
If you follow your STRs on the phone and then select the console, you should see the 403.
Comment 5•5 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #2)
Honza, are there known issues where the netmonitor will only show incomplete request information because we don't receive any update after the request creation?
Yeah this is a known issue. See Bug 1637188
Description
•