Closed
Bug 154784
Opened 22 years ago
Closed 21 years ago
Proxy: port-specific "no proxy for" settings (cf NN4.77)
Categories
(Core :: Networking, enhancement, P4)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: liam_a_oconnell, Assigned: darin.moz)
References
Details
(Keywords: helpwanted)
(platform/OS should probably be All/All, but I'll leave that to TPTB) Under NN4.77, it is possible to create a "no proxy for" entry of the type www.foo.com:81 which means that the proxy will be used for accesses to www.foo.com(:80), but not for access to www.foo.com:81. This is useful/necessary in some firewall configurations, if one doesn't want to hack up a .pac file. This does not appear to work in mozilla. It should, if only for ease-of-migration reasons. At the moment I have to constantly switch back and forth in the prefs dialog. (apologies if it does and I'm just too stupid to figure out how, but I asked on n.m.u.general and got no positive response)
+4xp. This is a really good catch.
Keywords: helpwanted
|
Assignee | |
Comment 2•22 years ago
|
||
-> me
Assignee: new-network-bugs → darin
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4
Summary: [RFE] Proxy: port-specific "no proxy for" settings (cf NN4.77) → Proxy: port-specific "no proxy for" settings (cf NN4.77)
Target Milestone: --- → Future
|
|
Assignee | |
Updated•22 years ago
|
Status: NEW → ASSIGNED
(In reply to comment #0) > (platform/OS should probably be All/All, but I'll leave that to TPTB) Yeah, please set someone Hardware/OS to All/All.
|
|
Assignee | |
Comment 4•21 years ago
|
||
WORKSFORME (this has been fixed for ages)
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
V/fixed: Mozilla 1.7.5 Finally read the code, and saw Darin's fixes for this via bug 80918. Also did some simple per-port block testing.
Status: RESOLVED → VERIFIED
Depends on: 80918
You need to log in
before you can comment on or make changes to this bug.
Description
•