Closed Bug 1666457 Opened 6 years ago Closed 6 years ago

Web extension `proxy.onRequest` listener is not called on `view-source:` requests

Categories

(WebExtensions :: Untriaged, defect)

80 Branch
defect

Tracking

(firefox81 affected, firefox82 affected, firefox83 affected)

RESOLVED DUPLICATE of bug 1657916
Tracking Status
firefox81 --- affected
firefox82 --- affected
firefox83 --- affected

People

(Reporter: 6ex, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:80.0) Gecko/20100101 Firefox/80.0

Steps to reproduce:

I'm the author of Container proxy extension which can assign a user defined proxy to a container so that all the requests from this container will use this proxy.
A user reported that when they open a source of a page (view-source) the request is not proxied.
After some research I identified that the request is still being issued within a container (correct cookies are sent) but the problem is that the listener defined in proxy.onRequest.addListener() is not being called for view-source urls.

See: https://github.com/bekh6ex/firefox-container-proxy/issues/28

Actual results:

Request is being done with default proxy settings.

Expected results:

Request to view the source should trigger listener defined in proxy.onRequest.addListener() and corresponding proxy settings should be used for this request.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Product: Firefox → WebExtensions

Hello,

I’ve managed to reproduce the issue on the latest Nightly (83.0a1/20200923212316), Beta (82.0b2/20200922183749) and Release (81.0/20200917005511) under Windows 10 Pro 64-bit and Ubuntu 16.04 LTS.

For testing I have proceeded with the following steps to reproduce:

  1. Installed the Container Poxy add-on
  2. Configured a proxy with SOCKS5 69.252.50.229:1080 and assigned it to a container
  3. Accessed https://www.wikipedia.org/ and checked the client IP in the web console under the request headers. The correct proxied IP was shown (69.252.50.229)
  4. Accessed the page source and also checked the client IP in the request headers. The incorrect non-proxied IP was shown

For further details, please see the attached screenshots.

Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
Attached image webpage.png —
Attached image source page.png —
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: