Open Bug 1802259 Opened 1 year ago Updated 3 months ago

[DNR] Consider distinguishing DNR and webRequest in cancel reasons and/or profiler

Categories

(WebExtensions :: Request Handling, task, P5)

Product:
WebExtensions
Component:
Request Handling
Type:
task

Tracking

(Not tracked)

People

(Reporter: robwu, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [addons-jira])

The WebRequest module specifies a cancel reason in https://searchfox.org/mozilla-central/rev/da01b81351132594e1ad84e50335162f5033c148/toolkit/components/extensions/webrequest/WebRequest.jsm#1085-1099, currently set to Ci.nsILoadInfo.BLOCKING_REASON_EXTENSION_WEBREQUEST. There is also a profiler marker there.

In DNR, the block reason BLOCKING_REASON_EXTENSION_WEBREQUEST is also re-used, because the current uses of the flag are merely interested in whether an extension blocked the request, regardless of API. I recently wrote about that at https://bugzilla.mozilla.org/show_bug.cgi?id=1794763#c1 .

The purpose of this bug is to revisit decision this later, to add DNR-specific reasons and/or markers if there is ever a desire to distinguish DNR-triggered cancelations from webRequest-triggered cancelations.

Blocks: 1687755
Whiteboard: [addons-jira]
You need to log in before you can comment on or make changes to this bug.