Do the proxy exceptions work by IP address or URL?

I'm having an issue in that using just the IP address (or subnet) in the proxy exceptions (Tools, Internet Options, Connections, LAN Settings) does not appear to work.
I've added the specific IP address, AND subnet but the traffic still goes to the proxy when I use the FQDN http://site.com instead. It's fine when I use the IP address in the address bar OR the site name in the exceptions.

The problem is that the full site name is huge and I'm concerned about the 255 character limit being hit too quickly. I am aware of the hack to up it to 1000 characters but I'm also aware of the performance hit this entails.

Could someone confirm for me that you MUST use the exact / wildcard of the address used in the address bar, and can't just put in the IP address?

I know it is not name resolution as I have put the site IP address in the HOSTS file and ensured that the correct IP is used.
LVL 10
Kieran_BurnsAsked:
Who is Participating?
 
pwindellConnect With a Mentor Commented:
IE has always been a disaster in the way it chooses to (or chooses not to) send requests to a proxy
The exceptions box is not for URLs,...the SIte Name is not going to be "huge" because the URL is not part of the site name.
Use the FQDN or the IP#.  You may have to use both.
You're probably better off forgetting the whole idea and place the FQDN in the Intranet Zone (Advanced button).   For FQDNs use this format *.mysite.com.  For IP#s you might have to include the http:// or https://, but I would try it without that first.
At our place I throw the whole idea out and go with Proxy Autodetection via WPAD.  By using WPAD and including the Firewall Client on the workstations (no FWC on servers) the browser only requires the first checkbox to be enabled in the LAN Settings,..everything else can be blank.  I never have any of these types of problems anymore.
0
 
Kieran_BurnsAuthor Commented:
Ultimately we've had to use partial names (with wildcards) it seems that IE will only accept what it sees in the address bar not what is sent.
Tried the suggested solution of using the zones - that didn't work either and WPAD is a non-starter as we have no access to the ISA Server.
0
 
Kieran_BurnsAuthor Commented:
Thanks for the help. You confirmed my worst fears :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.