[go: nahoru, domu]

Open Bug 452752 Opened 16 years ago Updated 2 years ago

New proxy settings need a Thunderbird restart

Categories

(MailNews Core :: Networking, defect)

x86
Windows XP
defect

Tracking

(Not tracked)

REOPENED

People

(Reporter: cdokolas, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: version 2.0.0.16 (20080708)

It seems that, in some cases, Thunderbird needs to restart in order to use new proxy settings. I was trying to fix an add-on update problem (updates were failing to download and subsequent update checks were failing) and I was furiously switching between Auto-detect and two different (manual) proxies (and I once used a settings URL). I restarted Thunderbird at some point early on, but then a manual setting that should work just wouldn't. I just restarted Thunderbird and everything was working again.

Reproducible: Didn't try




I'm sorry I can't provide more information. I don't have the time right now to test which combinations of proxy switching produce this problem.
Please provide a screen snapshot of your proxy prefs.

Regarding the "takes effect after restart"
Probably, you are using SOCKS, and it is a known bug where SOCKS changes don't take effect right away... (which I can't seem to find in bmo right now...).

Basically, if you had started some networking before you changed the prefs, you might not see the changes take effect until some underlying networking stuff is restarted. Obviously quit->restart solves that.
Ah, then it's SOCKS. What happened is that I had configured a SOCKS proxy that didn't work (temporarily) and tried to switch to a plain web proxy. Perhaps Thunderbird insisted using the SOCKS proxy (I suppose SOCKS is preferred over plain proxies?).

I'm marking this as RESOLVED. Just check that the new status is correct. Thanks.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
REOPEN... this is a real issue for thunderbird. it should take effect immediately, but it doesn't in some cases. Since I don't see a similar bug in TB, lets keep this one open for now.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Component: General → Networking
Product: Thunderbird → MailNews Core
QA Contact: general → networking
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.