Current Position:Home > Safari on Mavericks with NTLM Proxy

Safari on Mavericks with NTLM Proxy

Update:11-30Source: network consolidation
we use a Bluecoat Proxy in our Company with NTLM Authentication.
I login to the Mac (10.9.2) with my AD Account.
The proxy is configured with hostname and port.
Surfing in Firefox and Chrome works without a problem.
If i sniff the traffic for this two browsers i can see that
both browsers use NTMLSSP for authentication to the proxy.
If i try to use safari i does not work.
If i want to open a website the behaviour is always the same.
The blue bar in the address field stops at specific point but then nothing happens.
Even after half an hour i do not get an error message or the website.
There ist just nothing happening anymore.
Has anybody an idea what the problem could be?

The Best Answer

I have this same issue, and I have posted requesting insight on it here as well. But this has been to no avail.
It seems the proxy breaks only on networked accounts.
If you use a local account the proxy (in my experience) works fine if set up normally as you would.
This is just something that I have tried that has worked for me, it may not work for you or anyone else.
Our proxy is a windows server set up with TMG2010 and a web proxy address that is different from the DNS name of the server machine.
Normally we enter into the web proxy address which is something like:
I had the idea to try entering the local network name of the proxy as the proxy server in the network settings, then set up the user name and password boxes as I normally would as well. This actually worked.
Although I am not sure what to take from WHY it works. DNS has no issues, so it seems to me the authentication through HTTP/HTTPS has broke.
I have also read that somewhere else explaining it more in-depth than I feel necessary here but I will link you: t-using-http-authentication
I have found the location to toggle the authentication on our TMG2010 server so now I'm just waiting until closing time to test.
I just realized that most people tackling these issues look at what could be the problem on the MAC OS X side/Client Side….maybe the web server/proxy could use a good update to support more authentication control/methods/error handling…but then again that is what happens when you have two big brands with different architecture and software competing for floor space.