Closed RonnyTNL closed 2 years ago
Additional domains trying to connect are at least:
contile.services.mozilla.com firefox.settings.services.mozilla.com content-signature-2.cdn.mozilla.net push.services.mozilla.com
So it looks like all 'startup calls' are bypassing the proxy setting.
Just reproduced on an other machine, same specs.
Perhaps it's possible to provide an option to proxy "all other" connections that don't fall into any of the containers? Such as the ones listed above or the browsing that happens via normal tabs outside of containers.
Thanks for filing this issue. Maybe, multi-account-containers should not touch the proxy settings if there is an existing proxy configuration. We will work on this in the next release.
Fixed in 8.0.3. This build is about to be released.
Sorry to bump this but when is 8.0.3 going to be released, corporate users behind firewalls that enforce proxy are severely limited by this as e.g. CRL and OCSP lookups fail, which causes security concerns and delay-load times.
Problem is NOT solved with 8.0.3 Repro on two machines:
Setup a strict proxy, and preferably a software firewall that will alert for connections outside the proxy.
Open firefox on a blank page. Navigate to "Tools" -> Addons and Themes and you'll notice a direct connection to load the installed extension images/icons.
Corresponding DNS request == addons.mozilla.org Also CRL/OCSP lookup seems affected (at least) == oscp.digicert.com
Setting Multi-Account containers to disabled removes this behavior.
Since latest update 8.0.2 Firefox which is configured to use a local proxy call's out directly to push.services.mozilla.com When I disable the Multi-Account-Container the issue disappears, when enabled again the issue returns.
Actual behavior
Firefox tries to bypass the configured local proxy settings
Expected behavior
Firefox should honor the 'default proxy' settings, unless multi-container specifies a different proxy (no page is loaded when behavior occurs).
Steps to reproduce
Notes