Closed Bug 1599941 Opened 5 years ago Closed 5 years ago

webRequest.BlockingResponse() does not work together with FetchEvent.respondWith() of a ServiceWorker

Categories

(WebExtensions :: Request Handling, defect)

71 Branch
defect
Not set
normal

Tracking

(firefox70 affected, firefox71 affected, firefox72 ?)

RESOLVED WORKSFORME
Tracking Status
firefox70 --- affected
firefox71 --- affected
firefox72 --- ?

People

(Reporter: jararaca283, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

I've created a min example on GitHub: https://github.com/KevinRoebert/webext_and_service_worker

  1. Install the web extension (it should remove tracking parameter from URLs)
  2. Copy the service_worker folder to a (local) server
  3. Navigate to the index.html?tracking=test on the server
  4. The extension removes the tracking parameter
  5. Revisit the site, with tracking parameter

Can also be seen in this video: https://www.youtube-nocookie.com/embed/tBCnV-_IKjE

Actual results:

A NetworkError exception is thrown.

Expected results:

The site should be loaded. If this is not possible, every tracking protection addon can't be used along with ServiceWorkers, also this bug does not occur on Chrome.

Component: Untriaged → Request Handling
Product: Firefox → WebExtensions

Hello,

I have managed to reproduce the issue based on the provided STR on the latest Beta (71.0/20191128221751) and Release (70.0.1/20191030021342) under Windows 10 Pro 64-bit.

On Nightly the issue does not seem to occur. In about:serviceworkers no service workers are registered and I’m unsure if it’s related or not.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Looks like this will get fixed by e10s service workers, bug 1588154 comment 2.

Status: NEW → RESOLVED
Closed: 5 years ago
Depends on: 1588154
Resolution: --- → WORKSFORME
Duplicate of this bug: 1817450
No longer duplicate of this bug: 1817450
You need to log in before you can comment on or make changes to this bug.