Bug 24365 – I get an error when logging into Squirrel Mail using HTTPS

• Status: UNCONFIRMED
• Component: New Bugs

[Doug Hill]

I am attempting to login to my Squirrel Mail account.

Steps to reproduce:
1.  I go to the login page using HTTPS protocol. e.g.
https://webmail.breaqz.com
2. I enter my username and password
3. Click the button "Login"

Results:
I get the following error;

"Safari can’t open the page.
Safari can’t open the page “https://webmail.mountainpalace.com/src/redirect.php”. The error is: “Operation could not be completed. (kCFErrorDomainCFNetwork error 303.)” (kCFErrorDomainCFNetwork:303) Please choose Safari > Report Bugs to Apple, note the error number, and describe what you did before you saw this message."

Looking up in CFNetwork.h, it says:
kCFErrorHTTPParseFailure      = 303

I am using Safari
Version 4 Public Beta (5528.16)

[Mark Rowe (bdash)]

Has this ever worked in Safari?  If so, when did it stop working?

[Doug Hill]

I was able to log into Squirrel Mail using HTTPS with no problem using Safari 3.2.1. It was only after upgrading to Safari Version 4 Public Beta (5528.16) that this stopped working.

[Doug Hill]

I'm now noticing some other interesting facts:

- The webmail I'm using is being hosted by Dreamhost.
- Using PowerPC build on G5 iMac, I'm having trouble just accessing many Dreamhost domains using HTTPS using Safari 4 Beta. e.g.
https://www.dreamhost.com
- These sites work fine with the same computer, network configuration, etc. using Firefox.
- I notice that the SSL certificate is invalid for those URLS, which prompts a herculean effort to get Firefox to actually access the site (but it does work fine).
- I wish I could figure out some other domains not hosted by Dreamhost that have invalid SSL certs so I could test this case.
- I should also mention that I'm having these problem when I'm behind my work's firewall. With no firewall I don't ave access problems.
- On Intel computer I'm having no problem just accessing the sites behind the firewall, but get the 303 error when logging into webmail.

[Doug Hill]

OK, after further investigation, ignore the above "Interesting Facts" regarding access issues on PowerPC. This is apparently due to some other issue involving Safari's use of an HTTPS proxy.

The issue with logging into webmail is still there however.

[Doug Hill]

Doing more testing, I have now narrowed this down to a problem when using an HTTPS proxy. If I use the same machine, OS, browser, etc. but bypass the HTTPS proxy, I don't get the errors I described in the original bug report. I can bypass the proxy by switching to a wireless network and different ISP. When I switch back to the corporate network connection (Ethernet) and use their HTTPS proxy I get the errors.

It should be noted:
- I didn't get these errors with Safari 3.2.1
- I currently don't get these errors when using Firefox, Camino, or Opera.

Something changed from Safari 3.2.1 to Safari 4 Public Beta that caused it to fail when using this HTTPS proxy.

[Chris A. Waters]

We've been working on an internal web application that uses a C# proxy class to fetch a Google chart using their chart API. We did this, because our application is built to work over HTTPS and, at the time, the charting API didn't support HTTPS requests. 

Our application works in all major browsers except Safari 4.0.2. It did work in the release version of Safari 4.