Problem Description In a server-based environment, I need to implement automatic updates for Mozilla Firefox, while maintaining strict outbound network control. The architectural requirement is as follows: • Only the update component should be allowed to access the Internet via a proxy. • The browser itself (user browsing sessions) must not inherit or use that proxy configuration. • The proxy configuration for the update mechanism should be logically separated from the browser’s network configuration. ⸻ The Issue In contrast to the update mechanism used by Google Chrome (Google Update / Omaha), where: • The updater runs as a separate system service • It supports dedicated proxy configuration • It does not inherit browser-level proxy settings • It allows granular control of outbound traffic exclusively for update operations In Mozilla Firefox: • The update mechanism is tightly integrated with the browser • There is no native, dedicated proxy configuration exclusively for the updater • Proxy configuration applies to the entire browser • It is difficult to implement an “update-only network access” model