Background services like safebrowsing, selfsupport, tiles etc. should start network connections after proxy credentials provided for browsing

UNCONFIRMED
Unassigned

Status

()

Core
Networking
P5
normal
UNCONFIRMED
10 months ago
2 months ago

People

(Reporter: mishra, Unassigned)

Tracking

51 Branch
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-would-take][http-conn])

Attachments

(3 attachments)

(Reporter)

Description

10 months ago
Created attachment 8834829 [details]
Capture.PNG

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.88 Safari/537.36 Vivaldi/1.7.735.46

Steps to reproduce:

Tried to delete these sites in about:config, but I cannot find them there. I also parsed all files of FireFox for these 2 sites, but got no luck - FF still tries to connect to these sites even my proxy username and password are saved.

I disabled everything trying to auto-update on FF startup, but FF still connects to these sites.


Actual results:

FF connects to mxr.mozilla.org and to search.services.mozilla.com and FF always asks to provide saved credentials for proxy connection. Annoying window with 


Expected results:

FF should not connect to any site upon startup until user asked for that.
(Reporter)

Updated

10 months ago
OS: Unspecified → Windows 7
Hardware: Unspecified → x86

Comment 1

10 months ago
Not an issue.
https://support.mozilla.org/t5/Protect-your-privacy/How-to-stop-Firefox-from-making-automatic-connections/ta-p/1748
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → INVALID
(Reporter)

Comment 2

10 months ago
Thanks for the prompt reply.

I'm sorry, but before I post this bug report, all necessary actions were taken according to the link you've provided. I disabled everything that relies on autoupdate feature in FF. I also could not find any mentions of dxr.mozilla.org in about:config, neither in compiled code of FF.

I guess that these 2 URLs are hard-coded into FF source code in some obfuscated manner and it is impossible to restrict FF from accessing them at the startup of FF by means of usual config page.

Please advise on future actions which I could take to disable FF from automatically accessing these 2 URLs upon the startup of FF.

Thank you for your efforts!
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
For the search.services.mozilla.com connection, set browser.search.geoSpecificDefaults to false and check if you still see the issue. The mxr mentions in the code fore Firefox 51 (what version are you using) are all in code comments. Did you visit mxr.mozilla.org (the code search) before? Then this could be a connection from the thumbnail generator which fetches the page to generate a screenshot for the most visited pages on about:newtab.
(Reporter)

Comment 4

9 months ago
browser.search.geoSpecificDefaults already was in false state, and I have seen no records with search.services.mozilla.com anymore, but now there is a new host to which FF is trying to connect aus5.mozilla.org:443

My home page was set to about:mozilla , first host FF trying to connect to is mxr.mozilla.org:443 and this invokes nasty window with proxy authentication dialog with saved credentials

Regardless my homepage set to about:mozilla or just blank, FF tries to connect to mxr.mozilla.org:443 two times, and next tries to connect to aus5.mozilla.org:443
(In reply to mishra from comment #4)
> new host to which FF is trying to connect aus5.mozilla.org:443
Because you mentioned that you turned off update checking, this might be the download / update check for the OpenH264 video codec plugin (required for video conferencing etc.). Set media.gmp-gmpopenh264.enabled to false and test if the issue is gone.

> My home page was set to about:mozilla , first host FF trying to connect to
> is mxr.mozilla.org:443 and this invokes nasty window with proxy
> authentication dialog with saved credentials
It might be better if you log these connection attempts:
1. Press the Alt key, open the menu Tools > Web Developer > Browser Console.
2. Enable everything under "Net".
(Reporter)

Comment 6

9 months ago
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #5)
> (In reply to mishra from comment #4)
> > new host to which FF is trying to connect aus5.mozilla.org:443
> Because you mentioned that you turned off update checking, this might be the
> download / update check for the OpenH264 video codec plugin (required for
> video conferencing etc.). Set media.gmp-gmpopenh264.enabled to false and
> test if the issue is gone.

Option media.gmp-gmpopenh264.enabled set to false, but FF still wants to CONNECT aus5.mozilla.org:443 on the startup.

> > My home page was set to about:mozilla , first host FF trying to connect to
> > is mxr.mozilla.org:443 and this invokes nasty window with proxy
> > authentication dialog with saved credentials
> It might be better if you log these connection attempts:
> 1. Press the Alt key, open the menu Tools > Web Developer > Browser Console.
> 2. Enable everything under "Net".

Here it is.

Headers:
Content-Type text/html; 
charset=us-ascii
Proxy-Authenticate Basic 
realm="proxy"
Proxy-Connection close

Accept */* 
Accept-Encoding gzip, deflate, br
Accept-Language en-US,en;q=0.5
Cache-Control no-cache
Connection keep-alive
Cookie _ga=GA1.2.2145043884.1486549011
DNT 1 
Host aus5.mozilla.org
Pragma no-cache 
User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

Call stack:
downloadXML/< resource://gre/modules/addons/ProductAddonChecker.jsm:147:5
	downloadXML resource://gre/modules/addons/ProductAddonChecker.jsm:87:10
	ProductAddonChecker.getProductAddonList resource://gre/modules/addons/ProductAddonChecker.jsm:334:12
	GMPInstallManager.prototype.checkForAddons resource://gre/modules/GMPInstallManager.jsm:107:5
	GMPInstallManager.prototype.simpleCheckAndInstall< resource://gre/modules/GMPInstallManager.jsm:204:29
	TaskImpl_run resource://gre/modules/Task.jsm:319:40
	TaskImpl resource://gre/modules/Task.jsm:280:3
	createAsyncFunction/asyncFunction resource://gre/modules/Task.jsm:254:14
	gBrowserInit._delayedStartup/< chrome://browser/content/browser.js:1334:7
After looking at the code, it doesn't seem possible to prevent this call. You could modify the url preference and point it to localhost to prevent the proxy dialog.
Mishra can you please see comment 7 from Sebastian?
Flags: needinfo?(cps_register)
(Reporter)

Comment 9

9 months ago
Created attachment 8843210 [details]
firefox start up connections

I've added to c:\Windows\System32\drivers\etc\hosts the following entries:

127.0.0.1 aus5.mozilla.org
127.0.0.1 mxr.mozilla.org
127.0.0.1 self-repair.mozilla.org
127.0.0.1 search.services.mozilla.com
127.0.0.1 tiles.services.mozilla.com
127.0.0.1 shavar.services.mozilla.com

but it didn't change anything.

The proxy authentication window is still popping out every time I start FireFox.

According to my WireShark, FF is now hammering one by one: tiles.services.mozilla.com, search.services.mozilla.com, shavar.services.mozilla.com and the last host self-repair.mozilla.org
Attachment #8843210 - Flags: feedback+
(In reply to mishra from comment #9)
> According to my WireShark, FF is now hammering one by one:
> tiles.services.mozilla.com,
See http://forums.mozillazine.org/viewtopic.php?f=7&t=2888321

> search.services.mozilla.com,
Set browser.search.geoSpecificDefaults to false but you might get the English search engines by default.

> shavar.services.mozilla.com
This is the safebrowsing service. Setting these prefs to false will disable its protection:
browser.safebrowsing.blockedURIs.enabled
browser.safebrowsing.downloads.enabled
browser.safebrowsing.malware.enabled
browser.safebrowsing.phishing.enabled

> self-repair.mozilla.org
Create browser.selfsupport.enabled and set it to false.

You might find these preference settings helpful: https://dxr.mozilla.org/mozilla-release/rev/ed3f666f580073edf76b538c3dde6badd81c7d40/addon-sdk/source/test/preferences/no-connections.json
Summary: FF always connect to mxr.mozilla.org and search.services.mozilla.org upon the startup → Background services like safebrowsing, selfsupport, tiles etc. should start network connections after proxy credentials provided for browsing
Component: Untriaged → Networking
Product: Firefox → Core
Whiteboard: [http-conn]
(Reporter)

Comment 11

8 months ago
Created attachment 8849543 [details]
user.js

In case anyone will have the same FireFox behavior, I have attached user.js file with all preferences included.

After I've applied this user.js file into my FF profile - nasty pop-up window with proxy creds disappeared. So, the file works like a charm.
Flags: needinfo?(cps_register)
Whiteboard: [http-conn] → [necko-would-take]
Whiteboard: [necko-would-take] → [necko-would-take][http-conn]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.