Currently Being ModeratedOct 27, 2011 2:17 AM (in response to Richard Liu2)
OK, I've figured out something that might be useful:
First, Safari 5.1.1 will just Crash-On-Launch when HTTPS connections are unavailable. And it's confirmed that this crash condition is related to extensions. If there is no extension installed, Safari can launch normally. This crash condition can be 100% reproduced, and it's something new in 5.1.1.
Second, the HTTPS over WiFi via Proxy is an old problem. And it's a system wide problem.
Third, in 10.7.2 this problem seemed go worse: When the first HTTPS connection fails, all sequence HTTPS connections will be blocked. Reconfiguration network interface (i.e. reconnect to ethernet) will NOT recover the HTTPS connections. The only way to solve this is reboot.
Currently Being ModeratedOct 27, 2011 3:55 AM (in response to Richard Liu2)
I've done some detailed test and now I can give a conclusion:
1. It's confirmed that sequence HTTPS connection will be blocked in Safari and Google Chrome after a failure HTTPS connection (due to proxy). And rebooting is the only way to recover connections.
2. My previous observation is wrong: this is NOT a system wide problem. FireFox is not affected. FireFox will return to normal and all sequence HTTPS connection can be proceeded without any problem when I reconnect to a valid network connection (i.e. ethernet), while the Safari and Google Chrome remained being blocked. And DropBox is NOT affected as well.
3. None of the solutions mentioned in other threads can solve this problem. Checking the "Auto proxy discovery" does not help. Delete ~/Library/Preferences/com.apple.security.revocation.plistfile does not help. Clean Keychain does not help either. I've created another account for testing.
4. It's apparently something related to some system built-in network services. Since the FireFox and DropBox both gets its' own Proxy implementation, while Safari and Google Chrome will take the system settings. It's also worth noting that the POP3-SSL connection in Mail.app is also blocked after a failure HTTPS connection.
Currently the ONLY valid solution is using FireFox instead.