Closed Bug 327599 Opened 19 years ago Closed 17 years ago

Proxy settings are not updated after changing Location (with a twist)

Categories

(Camino Graveyard :: OS Integration, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mozilla, Unassigned)

Details

(Keywords: qawanted)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0

This bug is very similar to 167900.  If I switch network location and connect to my VPN Camino has to be restarted to work.  All other browers work.  There is one thing that might be different in my case.  I am using the CiscoVPN client to connect to my office rather than the built in VPN client.  When I connect, I have to first switch Network locations THEN connect to the VPN.  Doing the other way round doesn't work because changing locations breaks the VPN connection.  Because of this, immediately after switching location, my proxy autoconfiguration server is not yet reachable.  Perhaps Camino is looking for it immediately after the event?

Reproducible: Always

Steps to Reproduce:
1.Switch to a location with autoconf.pac server that isn't reachable (pull the plug on the network cable maybe?)

2. Make the server reachable

3. Attempt to browse.  You will get not connected error.  Not sure how Safari handles this, but it does seem to work.
Keywords: qawanted
There's been a report of similar behaviour (bug 374748) with the 1.1 beta, but that report says that the 1.1 alpha actually worked fine.

Brendon, can you download the 1.1 alpha and the 1.1 beta and see if you have the same problem?

ftp://ftp.mozilla.org/pub/mozilla.org/camino/releases/

Thanks,
Chris
QA Contact: os.integration
Assignee: mikepinkerton → nobody
Fixed in 1.5RC2
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
WORKSFORME since we don't know specifically what fixed this.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.