1495360 - At exit time firefox tries to connect to incoming.telemetry.mozilla.org without respecting proxy settings

Status: RESOLVED WORKSFORME

(Toolkit :: Telemetry, defect)

Description

[github.com]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180928054912

Steps to reproduce:

Exiting with ctrl-Q.


Actual results:

Firewall log shows direct outbound connection attempt:

Oct  1 08:24:57 mysystem kernel: IN= OUT=eth0 SRC=1.2.3.4 DST=52.10.55.151 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=50727 DF PROTO=TCP SPT=36922 DPT=443 WINDOW=14600 RES=0x00 SYN URGP=0 

DNS query log shows:

01-Oct-2018 08:22:07.098 queries: info: client 1.2.3.4#98765 (incoming.telemetry.mozilla.org): query: incoming.telemetry.mozilla.org IN A + (5.6.7.8)



Expected results:

The firefox should have used the proxy settings (of HTTPS probably, since it tried to connect to port 443).

Comment 1

[Daniel Stenberg [:bagder]]

Thanks,

What proxy type/config were you using? I'm not totally sure it matters, but it will certainly help when trying to reproduce and track down this issue.

Comment 2

[github.com]

> Thanks,
> 
> What proxy type/config were you using? I'm not totally sure it matters, but
> it will certainly help when trying to reproduce and track down this issue.

Thanks for the needinfo request.

My proxy settings is "manual proxy configuration". The "HTTP proxy" value is "localhost.mydomain". The port is 3128. On that port a squid proxy is listening. The "Use this proxy server for all protocols" checkbox is selected. I have certain hosts configured in the "No Proxy for" box (Mostly intranet hosts, including localhost). No any host is on the exception list in the mozilla.org domain. Neither mozilla.com, amazonaws.com. It may be important if the proxy search itemize the DNS name resolution result of incoming.telemetry.mozilla.org and tries to find the proxy by each CNAME record. (I do not know how the proxy search is working but just in case.)

Comment 3

[github.com]

I was watching in one screen the firewall log and from the other terminal session ending of the firefox program (started from that console). I just realized that the firewall log entries were still coming after the firefox program ended to run. How can it be? After small investigation I found that it is not the firefox executable directly which does not respect the proxy settings. The firefox at the end of its run lunches a program called "pingsender". That program is not respecting the proxy settings.

Comment 4

[Kershaw Chang [:kershaw]]

Change the component, since this bug is actually about another executable pingsender.

Comment 5

[Chris H-C :chutten]

Ah-ha, yes, the pingsender has no knowledge of your proxy configuration, I'm afraid. It doesn't have any configuration and is attempting its best-effort attempt to try and send a ping. If it fails, Telemetry will pick up the workload and do a better job the next time you run it.

This doesn't signify an unrecoverable error or cause problems with the proper working of Firefox, and can be ignored.

Does that help resolve this issue?

Comment 6

[github.com]

That is right it is not a failure, the firefox is functioning as expected. The only thing is that I am picky not only the inbound, but the outbound IP connections, so I found this uncategorized connection attempt alarming. At the time of opening the issue it wasn't clear that it is not the main firefox image that makes the direct connection atempt. I would leave to you how to handle that situation (if any action is needed at all), from my side I consider the issue being resolved.

Comment 7

[Chris H-C :chutten]

I consider it resolved as well. I wouldn't be opposed to pingsender becoming configurable somehow, but I wouldn't be able to prioritize the work over what I'm currently doing... which will make pingsender unnecessary completely in I'm hoping just a few months : )