Provide path and query components to non-https URLs

REOPENED
Unassigned

Status

P3
normal
REOPENED
2 years ago
26 days ago

People

(Reporter: mattw, Unassigned)

Tracking

(Blocks: 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [proxy] triaged)

(Reporter)

Description

2 years ago
The path and query components should only be stripped for https:// URLs, and only when the preference network.proxy.autoconfig_url.include_path is set to false.

Reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_(PAC)_file#Parameters
(Reporter)

Updated

2 years ago
webextensions: --- → ?

Updated

2 years ago
webextensions: ? → ---
Since our FindProxyForPAC() implementation is non-standard (see bug 1381290 and others), we should not fix this.

It is more useful for addons to have the entire URL at all times, rather than some of the URL sometimes and all of the URL at other times. Having the URL at all times is also analogous to what legacy addons had with nsIProtocolProxyFilter.applyFilter().

Since addons are trusted, there is no reason to hide path and query components or any other part of the URL from the addon. The stripping of this info for traditional, server-hosted PAC files may have had to do with security precautions. Since our FindProxyForPAC() is hosted within the locally-hosted addon itself, there's no added security risk by providing this info. Indeed, it is also available to the addon via webRequest API listeners.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
(Reporter)

Comment 2

a year ago
Currently the path component of the URL isn't provided at all, and I think you're suggesting that it should be provided for all URLs, correct? If so, we would still have to make that change.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
> I think you're suggesting that it should be provided for all URLs, correct

Yes. Do we need a new bug?
Priority: -- → P2
Depends on: 1409592

Comment 4

a year ago
Could anyone points me how I may fix it? This bug makes my addon almost unusable. I would like to fix it myself if I could.

Updated

a year ago
Priority: P2 → P3
Status: REOPENED → RESOLVED
Last Resolved: a year ago9 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1409878

Updated

5 months ago
Product: Toolkit → WebExtensions
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Duplicate of this bug: 1494823
You need to log in before you can comment on or make changes to this bug.