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)

29 Branch
x86_64
Windows 8
defect

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.
(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).
Component: Untriaged → Networking
Product: Firefox → Core
Whiteboard: [bugday-20140120]
Whiteboard: [bugday-20140120] → [bugday-20140120][necko-would-take]
Priority: -- → P5
Severity: normal → S3

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.