Open
Bug 959949
Opened 11 years ago
Updated 1 year ago
`No Proxy For` too one sided to be useful
Categories
(Core :: Networking: Proxy, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: kyle.leet, Unassigned)
Details
(Whiteboard: [bugday-20140120][necko-would-take])
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140114030236
Steps to reproduce:
No Proxy for supports forwards matching, but not backwards. I'd like to match protocols, and only forward for some and not all.
Actual results:
Nothing matched when I tried port numbers, or starting protocols in the list.
Expected results:
Firefox should have potentially automagically determined that :443 designates a port number, or https:// should be forward matched.
Reporter | ||
Comment 1•11 years ago
|
||
(In reply to Kyle Sanderson from comment #0)
> No Proxy for supports forwards matching, but not backwards. I'd like to
> match protocols, and only forward for some and not all.
I'm sorry, at the moment it supports backwards matching, not forwards (which is what I'd like).
![]() |
||
Updated•11 years ago
|
Component: Untriaged → Networking
Product: Firefox → Core
Whiteboard: [bugday-20140120]
Updated•9 years ago
|
Whiteboard: [bugday-20140120] → [bugday-20140120][necko-would-take]
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
Comment 3•1 year ago
|
||
Moving bug to Core/Networking: Proxy.
Component: Networking → Networking: Proxy
You need to log in
before you can comment on or make changes to this bug.
Description
•