Welcome to the MacNN Forums.

Drakino · Jul 30, 2003, 02:19 PM

I've tried different proxies, including Squid on my local machine. I've redownloaded and reinstalled Safari. And still, the same error every time if I try to access any https site. The proxies I use don't require authentication, and I do remember Safari working on secure sites a while back.

Any ideas?

cpac · Jul 30, 2003, 03:20 PM

this isn't a Safari problem so much as a problem with your proxy/setup.

Safari works just fine on https sites for me.

Drakino · Jul 30, 2003, 04:54 PM

this isn't a Safari problem so much as a problem with your proxy/setup.

I beg to differ. At one time, Safari worked fine. Now it dosen't. When exactly it broke, I am not sure, but a reinstall via Safari.pkg from Apple fails to resolve the problem. Camino, Mozilla, IE, and OmniWeb 4.0 continue to work fine, using the same proxy, while for some unknown reason, Safari broke.

I have tried 3 proxy solutions and about 6 hosts with no resolution thus far. The solutions were either Squid on a remote server, Squid on my local machine pointing to one of the 6 servers, or a MS Proxy server on a remote server. In all cases, no proxy authentication is needed.

Safari works just fine on https sites for me.

Thats nice. I'm sure Apple wouldn't have released Safari if HTTPS support had a major problem. Something happened with mine, and I am trying to find a resolution. The error posted above is rather cryptic, and may be pointing to a deeper problem that I would like to find on my system.

cpac · Jul 30, 2003, 05:18 PM

Originally posted by Drakino:
but a reinstall via Safari.pkg from Apple fails to resolve the problem.

Have you tried deleting preferences/support files and seeing if that doesn't fix the problem?

reinstalling the app itself doesn't necessarily do that much.

Also, could you be more specific about which OW version you're using? 4.5 uses WebCore just like Safari, and might reveal if the problem is there or elsewhere...

Drakino · Jul 30, 2003, 06:22 PM

Originally posted by cpac:
Have you tried deleting preferences/support files and seeing if that doesn't fix the problem?

Also, could you be more specific about which OW version you're using? 4.5 uses WebCore just like Safari, and might reveal if the problem is there or elsewhere...

I deleted the Safari app, ~/Library/Safari and ~/Caches/Safari, then reinstalled Safari. Same issue is happening.

I had OmniWeb 4.x (can't remember the exact version, was one without the Safari Webcore). I just tried the newest 4.5 SP, and it works fine going to secure web sites.

Any other guesses?

geekwagon · Jul 31, 2003, 12:54 AM

Safari has never supported doing HTTPS over a proxy. Because HTTPS is encrypted it is handled completely different from HTTP by the proxy server. Basically the proxy server just allows you to more or less direct connect to the remote server, unlike HTTP where you talk to the proxy server and it talks to the remote server for you.

Safari totally ignores your proxy setting in the System Preferences for HTTPS proxy. It will try to do a direct connect to the site from your machine (DNS request and all) rather than sending the request to the proxy server to be handled. Therefore, I guess probably what changed is your network admin started disallowing direct connections on HTTPS(443) at the firewall and forcing the browser to go via the proxy server. Lots of older proxy setups were designed to only work with HTTP and to just allow clients to direct connect on HTTPS because until the last few years proxy servers haven't supported proxying https at all. OmniWeb does work though because this is part of the networking code which Omni replaced with their own. Omni just uses the rendering engine from Safari.

I have heard that Konqueror also had this bug until just recently. I don't know for sure on that one though (read it on a different forum). I DO know for sure that Safari has never had HTTPS proxy support. I certainly hope that they add it soon, though.

Drakino · Jul 31, 2003, 12:15 PM

Originally posted by geekwagon:
Safari has never supported doing HTTPS over a proxy. Because HTTPS is encrypted it is handled completely different from HTTP by the proxy server. Basically the proxy server just allows you to more or less direct connect to the remote server, unlike HTTP where you talk to the proxy server and it talks to the remote server for you.

Aha, I think I know the problem. Or, why I thought Safari was working. When I first started using it, I was only using it for internal sites, several that use HTTPS. As I moved over more and more of my browsing, I eventually hit this limit.

I really wish Apple took proxies more seriously. How else are they going to gain any market acceptance inside a corporate environment?

Jonesy · Jul 31, 2003, 02:59 PM

I have the same problem. All of the mac users at work cannot use Safari to browse https sites even with the correct proxy settings.

OmniWeb has been working fine for the last few SPs.

Hope Apple start using Omni's fixes to Konqueror soon

Arkham_c · Jul 31, 2003, 03:16 PM

Send Apple feedback! This is an issue for me at work as well, since all traffic must go through the proxy.

ppmax · Jul 31, 2003, 05:08 PM

works for me (every day). my company provides web/https access to our exchange servers. have never had a problem.

i dont use a proxy.

geekwagon · Aug 1, 2003, 03:15 PM

Woohoo, I can now say that it seems that Safari in the latest panther build DOES work with https via a proxy. Hopefully, this means we will be getting a 1.1 release that fixes this bug soon on Jaguar.