Bypass proxy settings ignored

Hi folks,
At work we connect to the web via web proxy (Squid by all accounts). If I set the proxy manually in my browser, everything works fine but I'd rather have that set at Network prefs level.
However, when I add *.local, 169.254/16 at Network prefs level and set Firefox (or any other browser for that matter) to use System Proxy when I call something like domain.local (setup using MAMP Pro) I get a 404 which suggests that it's not ignoring my set prefs.
Any ideas why this is happening?

I forgot to mention that, when I use Automatic Proxy Configuration, the above issue exists. But if I use "Web Proxy (HTTP)", the Bypass blank works.

Similar Messages

Bypass Proxy not ignoring proxy

Hi,
I am connected to the internet through a http proxy but regularly have to connect to local IP's that do not go through the proxy.
I put the IP's of the machines I want connect to in the "Bypass proxy settings for these Hosts&Domains" section in the Proxies tab in Advanced Network Preferences however my browser still insists on trying to use the proxy.
Disabling the proxy allows me to connect to these machines but obviously this prevents me from browsing the web at the same time.
Could somebody advise me on this? Am I missing something or doing something wrong?
Thanks
Kev

I am connected to the internet through a http proxy but regularly have to connect to local IP's that do not go through the proxy.
I put the IP's of the machines I want connect to in the "Bypass proxy settings for these Hosts&Domains" section in the Proxies tab in Advanced Network Preferences however my browser still insists on trying to use the proxy.
Disabling the proxy allows me to connect to these machines but obviously this prevents me from browsing the web at the same time.
Could somebody advise me on this? Am I missing something or doing something wrong?
I would expect the Proxy settings to affect things like your browser. Are you attempting to connect to other web servers local network?
At work, I connect to local Macs using Bonjour and company systems using the company DNS names, so I put
local
companydomain.com
192.168.1/8
The 'local' is for MacComputerName.local addressing for other Macs on my local subnet, where MacComputerName is set in System Preferences -> Sharing -> Computer Name:
The 192.168.1/8 specifies a subnet to be ignored. This might be what you want to try, substituting your subnet. The /8 is because my netmask is 255.255.255.0. If you have a different netmask, you need to adjust the /n accordingly.

Strange info in "Bypass Proxy Settings for These Hosts and Domains"

For my Mac Mini my Network IP Address always has a self-assigned 169.254 number that I cannot change. Strangely, this same IP number is similar to info that is in the Proxies section (of Network Settings) under "Bypass Proxy Settings for These Hosts and Domains".
No matter what I do, this info (*,local, 169.254/16) appears in my Network Settings in the Proxies section under "Bypass Proxy Settings for These Hosts and Domains". (I tried removing the info and it would cause the "Configure Proxies" selection to default to "Always Use PAC File". Had to go back and retrash all the plist files to have Proxies go back to "Configure Proxies-Manually". Still, the info (*,local, 169.254/16) continues to appear in the "Bypass Proxy Settings for These Hosts and Domains" section and my IP address is always a 169.254 number.)
Comcast cable modem via direct hardwired Ethernet works fine with my other computer, so not the modem. Also, other computer does not have any info in the "Bypass Proxy Settings for These Hosts and Domains" section.
Installed a fresh copy of OS X 11.5 on a new hard drive. Still the same problem.
I posted this issue before but only got one responder and the problem still exists. Any clues? Somebody must know about this stuff. Help please.
Thanks

When your Mac wakes up, it does not yet have an IP Addresss. It wants to send a request to a Router for an apprpriste IP address to use now. But it needs to have an IP address (like a return address) to receive any messages. So, ... wait for it,
... it (your Mac) makes one up. There are rules that ensure it is a random address, but they always start with 169.254. It is on the same subnet with any low-order 16 bits This is the "self-assigned" range of IP Addresses. This address is only good for talking on a local network segment, for things like asking for a valid IP Address from a DHCP-enabled Router.
In most cases, on most networks, the 169.254 self-assigned IP Address is replaced by a valid Local IP Address such as 192.168.xxx yyy or 10.0.xxx.yyy so quickly that you never even see the 169.254 Address.
If you do see the 169.254 Address, it can be read as "Nobody will talk to me" or "Nobody will give me an IP Address". When you have this IP Address for more than an instant, you should suspect bad cables for Ethernet connections, bad signal strength or interference for wireless, Router configuration problems, or Mac configuration problems.
Mac configuration problems are often solved by using the "Assist Me" button is System Preferences > Network and choosing to set up again.
Another diagnostic is to try using Network Utility and the Ping function, and Ping-ing the address of your Airport base Station, often 192.168.0.1 or 10.0.0.1 or similar. This will tell you if the Router is reachable, or there are cabling/wirelss signal problems.
In this case, proxies are not an issue, and are simply a distraction from the real problems.

Bypassing proxy settings for IPv6-adresses.

My MacBook is currently connected both via IPv4 and IPv6, and I prefer using a squid-proxy when surfing. Alas, my proxy only supports IPv4.
In network preferences I can type in hosts to bypass proxy settings for, but I'd like to do this for every single IPv6 host. Any solutions?
Martin

The format should be comma-delimited, like:
<pre class=command>localhost, *.domain1.com, www.domain2.com</pre>
However, IIRC, Network Preferences is pretty tolerant - it'll accept most forms of input and will reformat it into something that makes sense to it.

Format for bypassing proxy settings

In Network Preferences, when you want to bypass proxy settings for certain domains, how do you separate the domains. are they comma separated?, or space separated?, or semi-colon separated?, one per line?.
TIA

The format should be comma-delimited, like:
<pre class=command>localhost, *.domain1.com, www.domain2.com</pre>
However, IIRC, Network Preferences is pretty tolerant - it'll accept most forms of input and will reformat it into something that makes sense to it.

Bypassing proxy settings does not work

I can't manage to get my Mac to bypass the proxy settings. My bypass settings are:
*.local, 169.254.0.0/16, localhost, 193.230/16, 192.168.0.0/24, 172.16.6.0/24
With these settings if I try to access 172.16.6.120, the server does not respond.
However if my settings look like this:
*.local, 169.254.0.0/16, localhost, 193.230/16, 192.168.0.0/24, 172.16.6.0/24, 192.168.0.252, 172.16.6.120, 172.16.6.130
I can access that IP address with no problems.
I also tried: *.local, 169.254.0.0/16, localhost, 193.230.0.0/16, 192.168.0.0/24, 172.16.6.0/24 and *.local, 169.254.0.0/16, localhost, 193.230/16, 192.168.0.0/24, 172.16.6.* with no success.
Can you please help?

Please update to the current Firefox 22.0 release.
*Help > About Firefox
*https://support.mozilla.org/kb/update-firefox-latest-version.
*https://support.mozilla.org/kb/Updating+Firefox
The Firefox 21 version that you currently run is no longer supported with security updates.
*It is important to update Firefox and add-ons to the latest version to get all security fixes.
*FoxyProxy Standard: https://addons.mozilla.org/firefox/addon/foxyproxy-standard/

How to know whether bypass proxy for local address is enabled in browser

Can anyone help me in finding out whether the check box "bypass proxy server for local address" in Internet explorer (Tools->Internet options->Connections->LAN Settings) is enabled from java plug in.
In my applet application if that checkbox is enabled then i have to throw a message saying that the checkbox is enabled.
Thanks in Advance
Regards
Vijay

We have been in discussions with Microsoft over the last few days on this issue - which is seen with Outlook 2007 versions onwards. Extract from resolution communication from Microsoft:
The issue you have raised is known as it has been reported and when you have a proxy set in Internet Explorer and “Bypass proxy settings for local addresses”, Outlook will attempt to connect to Office 365 directly – like the bypass rule would apply.
Because the direct connection is blocked in the Firewall, Outlook needs to have the connections going in Timeout before attempting to connect using the Proxy.
Your network trace proves the issue.
Microsoft have scheduled a fix for Outlook 2010 in February 2014 cumulative update. A fix for Outlook 2013 will also follow, but Outlook 2007 will not be addressed because it is in Extended Support.
There are two possible workarounds for this behaviour:
First, and I wouldn’t recommend it, is to allow Direct traffic through the Firewall to Office 365.
The advantage of this approach is that it will be done centralized and it will impact everyone immediately.
Information about the O365 IP addresses
There are two downsides to this behaviour:
1. First you need to maintain the Firewall exceptions as IP from O365 server can change without notice
2. Second, winhttp traffic may go through both proxy and direct and this can cause unforeseen behaviour.
The second approach is to use a proxy pac instead of manually setting in the proxy and the exceptions.
The advantage is that you will have centralized method to control how winhttp traffic goes and the issue will not be experienced anymore.
If a single pac does not be fit, you can configure proxy pac files for each site requirements and use an IIS server to store it.

Bypassing proxy while connecting local servers

I have a proxy server 172.22.6.26 with port 80. This is set for http, https, ftp, socks, gopher in system preferences->network->ethernet->advanced->proxies.
I am running apache server from eclipse on my macbook pro. Macbook pro ip is 172.22.4.33. When I tried to fire a request using soap ui to http://172.22.4.33:8080/service, soap ui is throwing an exception saying ConnectionTimeoutException: Connect to 172.22.6.26
I dont want soap ui to connect to my local server through the proxy server. I checked the proxy setting for soap ui and it is not enabled.
How can I bypass proxy settings when a request is made to my localserver or to another apache server running on machine in same network(172.22.4.81)?
I tried putting 172.22.4.33, 172.22.4.81 in Bypass proxy settings for these Hosts & Domains: in system preferences->network->ethernet->advanced->proxies
Can anyone please help?

Hi..Thanks for your reply.
I tried what you mentioned. But still had the same issue.
Soap UI gives error as below
Wed Jan 02 12:36:15 GMT+05:30 2013:ERROR:org.apache.http.conn.ConnectTimeoutException: Connect to 172.22.6.26 timed out

Mail.app does not bypass proxy

I dont know if this is a bug or if I have done something wrong..but Mail is not able to bypass proxy for the my imap server which I have specified in the Network Preferences..If I disable the proxy, it connects to the server..but when proxy is enabled, it doesnt bypass for the domain I specify in "Bypass proxy settings for these Hosts and Domains" and gives and error..whats wrong?

I'm having the same problem;
Is there a specific format i'm supposed to enter the proxy exceptions in?
I thought that might be the problem

Bypass Proxy for Local Addresses - Office 365 connection/ Outlook 2010

This is a strange one. Connectivity to Office 365 within our netwotk works fine although very slow for outlook 2010 client to initially connect. Once connected, it works ok. I have done a netwotk trace using netmon to see if i can identify
the reason for the slow startup (2 mins minumum for profile to load and for outlook to connect to exchange). The trace tell me that my local pc tries to make a direct connection to the office365 external IPs first, then tries the TMG proxy. Once it hits the
proxy, it kicks into life and works.
So it looks to me like it thinks the external IP address of office 365 is an internal address and spends it time trying all the ip addresses until it trys the proxy. At this point, the
Bypass Proxy Server for Local Addresses is ticked.
As soon as i untick this box, all traffic heads directly to the proxy and of course it connects like lighting. The exchange settings proxy is set in outlook for "on fast networks, connect using HTTP first, then connect using TCP/IP" (tick
is on) and the same for slow networks.
I cant for the life of me work out why it tries to connect directly to the external IPs first and not connect via TMG until i untick the
Bypass Proxy Server for Local Addresses
Would love any ideas that may assist.

We have been in discussions with Microsoft over the last few days on this issue - which is seen with Outlook 2007 versions onwards. Extract from resolution communication from Microsoft:
The issue you have raised is known as it has been reported and when you have a proxy set in Internet Explorer and “Bypass proxy settings for local addresses”, Outlook will attempt to connect to Office 365 directly – like the bypass rule would apply.
Because the direct connection is blocked in the Firewall, Outlook needs to have the connections going in Timeout before attempting to connect using the Proxy.
Your network trace proves the issue.
Microsoft have scheduled a fix for Outlook 2010 in February 2014 cumulative update. A fix for Outlook 2013 will also follow, but Outlook 2007 will not be addressed because it is in Extended Support.
There are two possible workarounds for this behaviour:
First, and I wouldn’t recommend it, is to allow Direct traffic through the Firewall to Office 365.
The advantage of this approach is that it will be done centralized and it will impact everyone immediately.
Information about the O365 IP addresses
There are two downsides to this behaviour:
1. First you need to maintain the Firewall exceptions as IP from O365 server can change without notice
2. Second, winhttp traffic may go through both proxy and direct and this can cause unforeseen behaviour.
The second approach is to use a proxy pac instead of manually setting in the proxy and the exceptions.
The advantage is that you will have centralized method to control how winhttp traffic goes and the issue will not be experienced anymore.
If a single pac does not be fit, you can configure proxy pac files for each site requirements and use an IIS server to store it.

Why does Web Start App ignore Proxy bypass/exception list in Proxy settings

Hi All,
I've been pulling my hair out on this one for a while now and finally decided to see if someone can help me out.
In my office I have a intranet of numerous devices and pcs connected. There is also a proxy server on the network to allow connection through the the internet. I have my proxy settings setup to bypass the proxy for any addresses on my intranet. This is set in the normal way by adding ( http://192.168.1. to proxy settings exception list in IE. This proxy bypass list works fine for all other situation except the following:
On my Intranet I have an embedded web server device I have been developing that has a java application deployed using web start. This application is a monitoring tool that allows the user to check the various settings and status of the embedded device. The problem is that when the app is launched for some reason web start tries to get the require jar file from the proxy instead of directly from the device, even when the IP address of the device it is trying to get it from is in the bypass list?? I don't think Web start is checking the exception/bypass list in the proxy settings to see if it should be using the proxy or not?? I can see this by using wireshark and inspecting the GET HTTP requests sent from my pc to the proxy server instead of directly to the ip address of the embedded device.
If I change my proxy settings to use a direct connection/no proxy (untick the "use proxy server for your lan" box in IE settings) then everything works fine. However this is not a workable option for my customers as they don't want to have to continually change these settings when connecting to this device and then to the internet (which is the whole reason of having the exception / bypass list).
I've tried many things including using the proxy settings in the Java console instead of getting them from the browser but the same thing occurs.
Any help would much appreciated, as I not sure if it is something I am doing wrong, or a possible bug, or just the way it is meant to work??
I'm using the following...
Java version: 1.6 1.6.0_17
Operating system: ( I've tried XP and Vista)

I have the same problem, please anyone can help?

Web service client ignores http proxy settings

I have a web service client using Weblogic's web service client library. I'm trying to instruct it to use a http proxy. I've set all the following system properties:
-Dhttp.proxyHost=127.0.0.1
-Dhttp.proxyPort=8080 -Dweblogic.webservice.transport.http.proxy.host=127.0.0.1 -Dweblogic.webservice.transport.http.proxy.port=8080
No traffic is passing through the proxy.
When the proxy is down, the application works fine too. I suspect that the proxy settings are completely ignored for some reason.
I'm using Weblogic 8.1 SP4 on a Windows XP box and JDK 1.4.2 (Sun's bundled JDK with Weblogic).

Sorry about the delay,
You just need to use the standard java http proxy properties, take a look at:
http://download-west.oracle.com/docs/cd/A97329_03/web.902/a95453/useservices.htm
Does this help?
Gerard

Proxy settings frequently being ignored

I've got a frustrating issue with proxies that I hope someone can shed some light on.
I've got a relatively normal networking set up (statically assigned IP address via local LAN), and any web access must be via a proxy. I've got my proxies set under networking options, and using Safari I can browse the web, and Software Update works. I have only one Location defined.
I also have a number of other pieces of software installed that access the web and supposedly use the proxies set under networking options. e.g. Version Tracker, Mac Fixit, and a couple of other lesser known pieces.
Now here's the annoying part; a lot of the time these pieces seem to ignore the proxy settings and try to go direct (I know this because I can see the packets bouncing off my gateway/firewall). Other times they will honour the proxy and work as expected (this seems to be the exception rather than the rule however :/ ).
For the life of me I can't figure out what the magic ingredient is when it all works as expected. When it doesn't work properly, I can go to the command line and "scutil --proxy" will show the proxy settings as they should be. But they seem to be either unavailable to the offending applications or the Location is screwed up or something.
Does anyone have any idea on why on earth this might be happening? I'd love to get to the bottom of this and have my proxies work consistently...

Well that prompted me to check again the most notable program I have that has this issue - Version Tracker.
So doing a "Check" results in a connect via HTTPS to the VT servers after the disks have been scanned, which works as expected and I can see the entry in my proxy logs.
CONNECT client.versiontracker.com:443 - DIRECT/66.179.48.104
Then clicking on one of the items that is available to update, which is supposed to load info about the package in the pane below the results, hits my firewall as it tries to go direct via HTTP. So VT is successfully using HTTPS, but not HTTP.
However, as stated originally, my HTTP proxy is definitely set and Safari, et al work when I try and test them. Now I know it's likely that VT itself has some issues in it's code, but I suspect there is something more than just a bug in VT going on here. I've noticed other apps not work as well (these failures are all HTTP). And sometimes VT works and returns the info screen (unless on some rare occasions VT decides to use HTTPS for these screens as well - however, I can't reproduce this; sometimes it works and sometimes it doesn't).
So programmatically speaking, is there more than one way for an app to get proxy details? Does the system cache this result anywhere? Is it possible for something to interfere with this process or possibly corrupt any cache, etc? It certainly seems odd that an app can get back (and use) the HTTPS proxy details correctly but not the HTTP proxy details. :/

Safari ignores proxy settings for AJAX requests?

I'm using Safari 4 on Mac OS X 10.5.7.
When I configure Safari's proxy settings (which redirect to System Preferences -> Network -> Advanced -> Proxies), all my page requests go through the proxy I configured, except for AJAX requests.
I configured an intercepting proxy (burp suite) to verify this, and indeed, AJAX requests are not being sent to the proxy. I double checked the exact same page on Firefox 3.5 on the same Mac with the same proxy being configured, and in this case the AJAX requests do go via the proxy.
For Safari, I configured the "Web Proxy (HTTP)" and "Secure Web Proxy (HTTPS). Is there anything else I need to do? Is this a bug in Safari?
Thanks in advance for all help.

I'm seeing the same problem. I use privoxy, a local security/privacy/ad-blocking proxy that lives on my computer. Firefox always sends its requests through the proxy, but Safari sometimes ignores the proxy settings. Vienna, my RSS reader, stops going through the proxy when Safari stops doing it. A restart fixes the problem for a while, but eventually the ads start showing up in Safari and Vienna.
I didn't start seeing this problem until Safari 4. I'm currently using the most up-to-date version of Safari, 4.0.3, with Mac OS X 10.5.8 and all other updates as of 12 Sep 2009. Privoxy is version 3.0.10, not the very latest, but it's working.

Shockwave Player ignoring proxy settings?

For security reasons, ALL outbound user traffic is proxied.
In at least some situations, the Shockwave player appears to
ignore browser proxy settings and make attempts to go
directly to Internet sites on ports 80,443,1935. This is filling up
our
firewall logs making them less useful for real
troubleshooting. The client should always use the HTTP proxy and
NEVER
attempt direct connections to Internet hosts. Can we control
this behavior on the client in any meaningful way? I have read:
http://www.adobe.com/devnet/flashcom/articles/firewalls_proxy02.html#
and what we're seeing appears to be default behavior. Surely
this can be controlled client side and we are not at the whim
of the way the client is called by HTML served up from who
knows?
For an example of this, see --this is a Viagra ad...sorry,
but this is the one I was able to track down;-):
http://ads.pointroll.com/PortalServe/?pid=511654F38020070808222931&pos=h&flash=9&redir=htt p://us.ard.yahoo.com/SIG=12jc7dq14/M=607608.11098438.11852106.8528710/D=sports/S=96625734: LREC/Y=YAHOO/EXP=1194540739/A=4834290/R=0/id=CTURL/*$CTURL$&r=0.7514780048609885

I am running into the same issue with a few
sites...especially since the TCP timeout to realize that is has to
revert to a proxy is not conducive. I would think a client side or
registry setting would fix this, but cannot find where to change
that. Any ideas?

Bypass proxy settings ignored

Similar Messages

Maybe you are looking for