Add HTTPS support

[GoogleCodeExporter]

What steps will reproduce the problem?
1. http://gmail.com

What is the expected output? What do you see instead?
Display the Gmail page, "unable to load" error

Please provide any additional information below.

When trying to enter to Gmail.com there are a error that show a "unable to 
load" error, I don't know the reason but the unable to load error is like 
this:

Unable to load: 
http://mail.google.com/http://mail.google.comhttp://mail.google.com/http://
mail.google.comhttp://mail.google.com/http://mail.google.comhttp://mail.goo
gle.com/http://mail.google.comhttp://mail.google.com/http://mail.google.com

Hope this help.

Original issue reported on code.google.com by danielro...@gmail.com on 13 Aug 2007 at 2:46

[GoogleCodeExporter]

Thanks for the bug report. It is probably because Google Mail uses secure
connections, which I haven't added yet. In the short term, a better workaround 
(like
saying "HTTPS not supported yet") should be added to avoid the weird error 
shown there.

The long term fix is to add HTTPS which I have planned for some point in the 
future
using the embedded Matrix SSL library, for example.

Original comment by richard.quirk on 13 Aug 2007 at 4:07

• Added labels: Milestone-Future, Component-Bunjalloo

[GoogleCodeExporter]

Yes, a message is better to know that Secure Connections is not supported still.
By the way, Hotmail work but you cannot log in because the keyboard doesn't 
have a @ 
key :)

Original comment by danielro...@gmail.com on 13 Aug 2007 at 8:44

[GoogleCodeExporter]

Well, I've added broken https now. 

If you go to, say, https://mail.google.com it shows nothing since connecting to 
port
443 without encoding the connection just gets you disconnected right away. 

I'm not sure if this is better or worse than before but at least it has set up 
the
framework for adding proper SSL support some day.

Original comment by richard.quirk on 18 Sep 2007 at 8:54

• Changed state: Started

[GoogleCodeExporter]

Correction: it shows the rubbish "unable to load https://mail.google.com" page.
Changes made in r329 and r330.

Original comment by richard.quirk on 18 Sep 2007 at 9:06

[GoogleCodeExporter]

I'm changing the milestone + title on this one.

Original comment by richard.quirk on 1 Oct 2007 at 9:11

• Changed title: Add HTTPS support
• Added labels: Type-Enhancement, Milestone-0_4
• Removed labels: Type-Defect, Milestone-Future

[GoogleCodeExporter]

oops, sorry for the spam (and getting your hopes up) should be 0.5...

Original comment by richard.quirk on 1 Oct 2007 at 9:12

• Added labels: Milestone-0_5
• Removed labels: Milestone-0_4

[GoogleCodeExporter]

would be nice to see this feature soon. No other browser supports SSL yet

Original comment by migam...@web.de on 3 Oct 2007 at 9:54

[GoogleCodeExporter]

SSL has been added in version 0.5.

I've used bunjalloo successfully to read my gmail account and send emails. The 
Google
log in process does not work in one go due to some strange redirect problems, 
so I
recommend using it via the mobile interface at http://www.google.com/xhtml

I'll keep looking into the problem but wanted to get this out ASAP so you guys 
could
start using it and give me feedback.

Original comment by richard.quirk on 11 Nov 2007 at 6:34

• Changed state: Fixed-release

[GoogleCodeExporter]

tried it to login to my uni-wlan. But couldn't connect to the startpage: 
"unable to
open: https://uniname.ac.uk"

Original comment by migam...@web.de on 12 Nov 2007 at 11:22

[GoogleCodeExporter]

That's disappointing. Any chance you'd be willing to help me debug it? drop me 
an
email at richard.quirk@gmail.com if you like.

Original comment by richard.quirk on 12 Nov 2007 at 8:48

[GoogleCodeExporter]

With thanks to migamiga for his help debugging it, I've released version 0.5.1 
which
has a fix for the problem.

If anyone's interested: comment #9 was caused by the SSL library completely 
rejecting
any certificate chains during the initial handshake without giving the user 
callback
(i.e. bunjalloo) a chance to say "I don't care, connect anyway". I've fixed it 
by
removing the error condition in the SSL library here: 
svn diff -c17 
http://bunjalloo-deps.googlecode.com/svn/trunk/matrixssl/src/sslDecode.c

Yes, it isn't the most secure thing in the world. It is as if other browsers' 
"The
certificate can't be validated, are you sure you want to continue?" pop up 
warning
automatically selecting "yes, continue".

Original comment by richard.quirk on 17 Nov 2007 at 11:39