Safari 7 do not authenticate on HTTPS proxy

here goes a list of similar problems, let's see if they have a feedback soon:

https://discussions.apple.com/thread/5469717?answerId=23513507022#23513507022&ac_cid=tw123456#23513507

https://discussions.apple.com/thread/5480093?tstart=0

https://discussions.apple.com/thread/5471325

http://stackoverflow.com/questions/19575183/system-proxy-not-working-on-os-x-mav ericks

running this command on terminal solved the problem for safari:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.UserNotificationCenter.plist

got it from this thread: https://discussions.apple.com/thread/3259747?answerId=16552271022#16552271022

Same problem here.

Proxy authentification works well with Chrome and Firefox. But Safari isn't able to connect with the correct proxy settings.

Even the Mac App Store and so on dosn't work....

Funny thing: www.apple.com works fine 👿 But nothing else works.

Same thing here.

I don't need safari to work, I can use Firefox or Chrome.

But many tools uses the safari authentification to run, e.g. maps and doesn't work now.

But it is strange that the AppStore runs with no problems. 😕

I also check another user, and there it works fine.
So I think there should be a keychain issue.

Any Ideas?

I also have the same issue, there is something weird with the system proxy (System Preferences -> Network -> Advanced -> Proxies)

Sometimes the HTTPS proxy is cleared.

Sometimes Mavericks presents me a form to fill proxy user/password.

Chrome works fine.

Safari won't work even when I provide the proxy user/password.

same for me.... i lost a few hours attempting to find out what the issue is within my Network Ethernet interface...to find out that it is an issue related to Safari 7 only.....

So moving to Chrome as of today

Hi, well I had the same problem after upgrading from mountain lion to mavericks.What i did is I installed authoxy

which keeps proxy overall system.Just try doing that and I definitely think that it will work.

Download and do step by step procedure from this link

http://davidtse916.wordpress.com/2008/03/14/a-step-by-step-guide-to-authoxy/

Hope this helps 🙂

(sorry about my english)

Only makes it clear how many people have a problem and Safari is doing nothing but forcing their problem upon the users.

WHY DOES APPLE MAKE ITS CUSTOMERS DO THE WORK ??

All of the suggestions require that I do this, open that, change this, reset that ... Opera, Chrome, Firefox all work perfectly - only Safari doesn't. It's super slow, has problem after problem loading a page, I have to refresh 3 or 4 times per page to get the whole page up ... so much for "x-times faster than..."

Again:

WHY DOES APPLE MAKE ITS CUSTOMERS DO THE WORK ??

THIS IS THEIR PROBLEM, NOT OURS !!

So many bugs is not a normal thing. In fact there has never been a buggier release by Apple to date. And judging by the bug, where Finder crashes after multiple drags of attachments to a network drive for storage, which has not been fixed since Lion, it is very unlikely most of the current bugs would ever see a fix. By the way, did you notice that the spelling autocorrect does not work in the Apple’s support forums. It is ironic, that I had to copy/paste in TexEdit to check this post for spelling errors. Outside of the subject here, but I could keep pointing out bugs in Mavericks, the list is really long.

Definitely seems to be something broken here. I have my system configured to use a Squid2.7 based proxy with Kerberos based authentication against my Windows 2008 server.

Now - before Maverick this used to work fine. Chrome continues to work fine.

I see the 407 on initial request, Chrome returns with the required authentication tokens (username/password), authentication succeeds, 200s ensue.

Safari however continually gets stuck at the 407 stage. It won't authenticate. It's not prompting to authenticate. It goes to open a page and then just sits there.. doing nothing.. as if it's waiting for me to step in and retrieve the web page myself...

My proxy settings are simple:

HTTP = 192.168.1.5 (example IP)

Port = 3128

Proxy server requires password = ticked

Username = my name

Password = my password

Bypass list = *.local, 169.254/16

Again - Chrome works without an issue from the same machine..

Same problem

- Safari doesn't work with https (I'm using firefox for posting this!!!)

- Some time Safari also stuck loading http pages

- App Store and Software Update doesn't work e doesn't login

- iTunes Store doesn't work

- iBooks doesn't login

- Maps doesn't search

We are under an authenticated proxy (squid 3.3.3)

Firefox, Chrome and Opera works fine.

Everithing works fine for MacOSX 10.5.X , 10.6.X, 10.7.X and 10.8.X clients

Hello,

I think I solved the issue. Open Keychain, find stored credentials for your proxy server (just write e. g. your proxy server name into a search field) and Copy these credentials (usually 2 records - HTTPS, HTTP) from Login keychain into a System keychain. It's usefull to keep credentials in both (login and system) keychains. If you just move credentials, then the some apps asks your for admin password when using proxy server. Now it works fine and no more problems with Safari, Outlook, etc.

I hope it helps,

Kremik

| can i ask where you learned to do this so i can read up on it. | I tried to Kremik's solution ?> and it worked for the first | few days and now im having problems again. | Getting desperate. Nowhere. But as I see that the above solutions doesn't solve my problem, I have just tried some dichotomic search like this: - login from another account so I verify that the problem come from my own account and not from the global osx system, nor from the Safari application itself. - backup my full Library folder for futur restauration. - define a set of potentially faulty files or folders (the test file set) - enter a test cycle which consist of: - remove the test file set from my account - (optionnaly) relogin or quit and relaunch Safari - try a safari https url (e.g. a google search) - if it works then the bad file is part of the deleted files - restaure all Prefences folder (thanks to the rsync command) - define a new smaller subset test file set I appear that: - deleting the Preferences files is sufficient to correct the problem. So it is not a Keychain problem - one doesn't need to logout, neither to quit Safari to create or solve the problem. So this make following tests much easier :-) - try to delete only com.apple.*.plist solve the problem (then restaure all) - try to delete only some apple prefs which seems not related to a specific application (e.g. to keep my Terminal prefs, ...) I finally see that simply removing the com.apple.security.revocation.plist solve my problem. The I post my first contrib on this list in the hope it is usefull for somebody else. Is it?? -- Maurice

I have the same problem with mac app store and safari.

I am having the same issue.