Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Site not being proxied at startup #179

Open
emily785 opened this issue May 18, 2022 · 2 comments
Open

Site not being proxied at startup #179

emily785 opened this issue May 18, 2022 · 2 comments
Labels
duplicate This issue or pull request already exists general help General Help/Support Question

Comments

@emily785
Copy link

Set firefox to display home page at startup
Set your home page to your favorite "what is my ip" page
Close Firefox
Start firefox
Site is not proxied, displaying your real ip

Is this documented somewhere? Working as intended? Not possible to fix?
Seems like a rather critical issue at least IMO.

If I happen to start firefox on a page I normally want proxied, I've just leaked my IP...

@ericjung
Copy link
Collaborator

ericjung commented May 18, 2022

It’s a known issue. Last time I looked into it, the problem was due to the way Firefox loads add-ons and their configurations. They are not guaranteed to be loaded and ready before network connections are made. I imagine ad-blocking add-ons have the same problem unless Firefox has made changes since I looked into it.

@erosman
Copy link
Collaborator

erosman commented Aug 29, 2022

It used to be the case that extensions were loaded first in browser start-up. There were occasions of long start-up times therefore browser engineers decided to load the browser first and then the extensions.

As soon as browser is starts-up:

  • it makes connections for its own use
  • Tries to load tabs if there are open tabs from previous session and browser is set to reopen them

At this time extensions are NOT loaded so they don't function. It is best to not set the browser to open previous tab on start-up if proxies are used.

Next, browser starts to load persistent listeners belonging to the extensions but not the extensions yet. At this time, network connections will be proxied but if they require user/pass by the extension, the extension is not loaded yet to provide them.

Next the extension is loaded, the extension gets the user/pass from the storage and the normal process starts.

The time it takes for the aforementioned depends on type of starts-up e.g. it takes longer on upgrades, the number of extensions that needs to be loaded by the browser, and computer specs.

Previously: #143

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists general help General Help/Support Question
Projects
None yet
Development

No branches or pull requests

3 participants