bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

No proxy for: Override proxy settings




12 years ago
5 years ago


(Reporter: galen Henderson, Unassigned)


Firefox Tracking Flags

(Not tracked)




12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060909 Firefox/
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060909 Firefox/

I am not sure if this is a bug report or a feature request.  This is probably expected behavior but changing the behavior would be great.  In the config dialog where you set the list of hosts and addresses, if an address is entered, it is only honored with an exact match of the url as typed in the url box.  I am a developer and often set up a local site which I override in my hosts file to point to my local development address.  Even though localhost and is set up in the bypass proxy settings, the hosts file is not consulted before comparing to this value.  If you type in the hostname that you have overriden to localhost, the request still goes down the proxy.  It would be great if the program resolved the hosts file first and compares the IP address to the list of bypass hosts.  I realize that this is another hit to the hosts file for every proxy request but this could possibly be cached in memory for best performance.

Reproducible: Always

Steps to Reproduce:
1.override a host in your hosts file to point to
2.enter into the bypass proxy textbox in settings dialog
3.enter the name of the host you have overridden into the url bar of firefox.
4.press enter or click go.  

Actual Results:  
The request is served by the proxy and the proxy is not bypassed.

Expected Results:  
I would expect firefox to know that the host is local based on a lookup of the hosts file.

Comment 1

10 years ago

Summary: Override proxy settings → No proxy for: Override proxy settings
While I suspect that this is intentional (doesn't make this closeable as it can still be a feature request), I can confirm this.

I add that this doesn't check DNS in general. For example, I am behind a proxy that needs a no proxy for *.iitb.ac.in (the university domain). When DNSed from within the network, these resolve to 10.*.*.* addresses. Putting a CIDR block ignore "" is not sufficient here; attempting to go to something.iitb.ac.in will still lead to an error.
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.