Closed Bug 189746 Opened 22 years ago Closed 22 years ago

Proxy: multiple selector system

Categories

(Core :: Networking, enhancement)

Product:
Core
Component:
Networking
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 43429

People

(Reporter: lists, Assigned: dougt)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030108
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030108

I'm continually having to go into Prefs->Advanced->Proxies to toggle the proxy I
want to use (or none at all), depending on work needs. Other external solutions
do exist (like custom/local autoconfig scripts), but I'd love for Mozilla to let
me define multiple proxy configs, and then select the one I want (at any given
time) from a toolobar drop-down box or similar.

Also, some facility whereby each browser instance could work with whatever proxy
profile had just been selected would be good... as opposed to all instances
being forced to use the same settings.

sTu.

Reproducible: Always

Steps to Reproduce:
Please look at both the depends and the duplicate bug. If this solves your
problem, please VERIFY.

*** This bug has been marked as a duplicate of 43429 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Depends on: 88218
Resolution: --- → DUPLICATE
Summary: Want multiple proxy selector system → Proxy: multiple selector system
Ben, The reason I'm not really keen to dupe against 43249 is that the summary of
that bug is specific to ISP configs. Mine is independent of that - just a way to
quickly switch proxies. There are some immediately relevant comments IN 43249,
but I'm not sure they're going to be considered given the summary of the bug.

I also looked at 88218 and 59969 - none of which are what this bug is meant to
be about.

??
Well, it depends on how far you want to take it. Some corporate users have this
problem, ALL multi-ISP users w/ proxy have this problem.

Look at bug 43429 comment #14 sounds like what you want.
Yes, that is exactly what I want, but I feel that comment is lot on that bug,
unles the summary of the bug is changed to suit. I think that if that comment is
to be actioned, it should go in THIS bug. They're two different (yet related)
requests.

??
lot -> lost
Stuart: I changed the summary of the other bug, can you verify this bug if you
concur?
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.