Please report any other irregularities here.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031105 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031105 If you change your networking underneath Mozilla while it is running (i.e. you do something like start a VPN which changes /etc/resolv.conf, etc), Mozilla relies on res_init to recognise the fact that resolution entries (e.g. DNS) have changed. That is fine and good, however, if you are using "automatic proxy configuration URL", this change doesn't cause it to go out and try to discover what's changed. We use "http://wpad/wpad.dat" as the totally emulates the WPAD support like Internet Explorer and Konqueror have. End effect: you have a working Mozilla at home, you VPN into work, and try to access a new site, Mozilla directly tries your home proxy server settings, and Mozilla reports "cannot access proxy server". It can be fixed either by restarting (obviously), or going into the proxy settings, and replacing the URL with something similar. e.g. "http://wpad.atwork.domain/wpad.dat" while I'm at work - even though my default domain (from /etc/resolv.conf) is "atwork.domain". It seems that URL is "sticky". Once it's got it, it doesn't give it up unless overridden. Reproducible: Always Steps to Reproduce: 1.see above 2. 3. Expected Results: When a name resolution change has occurred (as triggered by res_init), Mozilla should retry downloading the automatic proxy configuration URL again - as the DNS entry may now point to a different host. See Bug 214538 for discussions I've had with others over res_init if you like.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.