1622875 - web-extension proxy APIs show incomplete requests in the network panel

Status: RESOLVED WONTFIX

(DevTools :: Netmonitor, defect, P3)

Description

[Andrea Marchesini [:baku]]

STR:

1. Install secure-proxy (but this can be done using any other proxy-related web-extesion).
2. activate it (better to use a @mozilla.org email address)
3. open the browser-toolkit -> network panel
4. open about:url-classifier
5. trigger an update of the mozilla provider.

I don't know if the bug is in devtools or in the proxy API, but I see this error message:

[firefox/index.js][debug] Firefox stdout: Handler function threw an exception: TypeError: can't access property "last" of undefined
Stack: _getWaitTiming@resource://devtools/server/actors/network-monitor/network-observer.js:1098:1
_setupHarTimings@resource://devtools/server/actors/network-monitor/network-observer.js:1323:28
_onTransactionClose@resource://devtools/server/actors/network-monitor/network-observer.js:1045:27
_dispatchActivity@resource://devtools/server/actors/network-monitor/network-observer.js:532:14
NetworkObserver.prototype.observeActivity<@resource://devtools/server/actors/network-monitor/network-observer.js:610:12
exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22
Line: 1098, column: 1
[firefox/index.js][debug] Firefox stdout: console.error: (new TypeError("can't access property \"last\" of undefined", "resource://devtools/server/actors/network-monitor/network-observer.js", 1098))

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:Honza, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks for the report Andrea!

It looks like the exception point to this line:
https://searchfox.org/mozilla-central/rev/fa2df28a49883612bd7af4dacd80cdfedcccd2f6/devtools/server/actors/network-monitor/network-observer.js#1102

(timings.REQUEST_BODY_SENT || timings.STATUS_SENDING_TO).last

Looks like both timings are null and the code should be ready for such situation.

Andrea, can you please provide more info for the first two steps.

Install secure-proxy (but this can be done using any other proxy-related web-extesion).
activate it (better to use a @mozilla.org email address)

What extension we could use for example?
What do you mean by activation?

Thanks!

Honza

Comment 3

[Andrea Marchesini [:baku]]

Andrea, can you please provide more info for the first two steps.

Install secure-proxy (but this can be done using any other proxy-related web-extesion).
activate it (better to use a @mozilla.org email address)

1. Install this extension and activate it. You must log in using your FxA account (better if you use a @mozilla.com email address) https://fpn.firefox.com/downloads/browser/latest/secure-proxy.xpi
2. when the proxy is active, follow the remaining of the STR in the bug description:
3. open the browser-toolkit -> network panel
4. open about:url-classifier
5. trigger an update of the mozilla provider.

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks Andrea!

Hubert, another one that needs triage.

Honza

Comment 5

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 6

[Hubert Boma Manilla (:bomsy)]

Hi Andrea,
Apologies i haven't gotten to this in a long while. The https://fpn.firefox.com/downloads/browser/latest/secure-proxy.xpi which seems to be the firefox private network extension which is no longer supported. Is there any other extension which i can use to reproduce.

Comment 7

[Andrea Marchesini [:baku]]

Not at the moment. Let's close this bug.