2008-09-15

Google Chrome - HTTPS and SSL Over Proxy Issues

by Anoop Engineer 14 comments




If you are a corporate user behind a proxy server and are using Google Chrome, you must be bitten by the Chrome HTTPS bug, at least once.
Trying to access HTTPS sites, like Gmail or your banking site through a proxy yields nothing but a blank page.
We just scanned the Google Chrome known issues page and saw this:
Google Chrome does not support SSL client authentication.
We know about this and don't currently have a fix.

Not very encouraging isn't it? There is no need to get discouraged, for here we give you three methods that will help you solve this issue:

Method 1: Using a Google Chrome Nightly Build

Though the Google known issues page says that they don't have a fix for this issue, this issue seems to be fixed in the Google Chrome latest daily night releases. Daily Night releases are developer releases made each day and may (will) contains bugs. I have used this one and it seems to work perfectly. Download Google chrome nightly builds here.

Method 2: Using the Portable version of Chrome

Some people report success using the portable version of Google Chrome. Download portable version of Google Chrome here.
Note: This method didn't work for us.

Method 3: Using a Microsoft Firewall Client


This method is applicable only if you are using Microsoft ISA Server as your proxy server.
Download Microsoft Firewall Client from here and install it. In the settings tab, specify the proxy ip address and enable it. In the Google Chrome proxy settings (Options -> Under The Hood -> Change proxy settings), disable any proxy configurations.

If you had any difficulties with any of the methods mentioned above, do let us know in the comments.

Comments 14 comments
Anonymous said...

methds 2 and 1 dosent work

Anonymous said...

Thanks, downloading nightly build did the trick. Thanks very much.

movie buff said...

i keep learning about more and more little advantages and quirks with Chrome, such as with security, for example; now if only they would take care of it's cookie management glitches...

New Trendy said...

thanks for this information. i need to setup proxy for some reason

Damodhar M said...

Method 1 is working fine for me.. thanks for the information

Wallpapers said...

nice information .. thanx for sharing...

rakeback said...

This issue is back with the new 1.0.154.48 version. Can't load any https pages, including Gmail and Google Analytics.

Anonymous said...

Seeing it here with Gmail and Chrome 2.0.172.30.

Doyles Room Rakeback said...

Method 1 also works just great for me

Anonymous said...

Using the ISA client would be a great idea, if only chrome was a real browser with settings of its one. Unfortunately we can't change chrome connections settings without affecting IE, because Chrome rely on IE connecting settings. Since the proxy works on IE without asking extra credentials, but don't work on other applications, like chrome, Google better learn how to use the proxy authentication, like IE does, and create a settings of its one for Chrome.

Sinn replica watches said...

Your post is really informative for me. I liked it very much.

Anonymous said...

I'm surprised companies have not sued Google for this issue. I have just spent several thousand pounds on new encapsulated checkout, EV SSL certificates and PCI compliance to assure my customers that we are committed to their security while shopping on my website.

But now it says the site is not secure and not to be trusted!!! IT BLOODY IS!!!!

So in retrospect, it would have been better to simply not bother (or pay for all this added security), and I am certain I will lose x% of visitors who are using Chrome...

*Adds "Site best viewed in Firefox" image....

Anyway, I will be sending my screenshots and webdesigner bills to google. Guess until it's fixed it's something we will all just have to live with.

Anonymous said...

Best fix for this so far:
http://www.google.com/support/chrome/bin/answer.py?hl=en&answer=100214

change the setting "check for server certificate revocation" in "under the bonnet" security options. Now the address bar goes green and also displays the organization's name.

However, this doesn't help much from a webmaster's point of view, as I'm sure as hell not going to plaster these instructions on my website in the vain attempt that people will do it and continue to my checkout....

Blast and botheration!

Joel said...

That works! Finally! I've been suffering with this problem for ages and that finally seems to have done it.

Thanks Anonymous.

Post a Comment

Subscribe feeds via e-mail
Subscribe in your preferred RSS reader

Advertise on this site Sponsored links

Subscribe feeds rss Recent Entries

Categories

Subscribe feed rss Popular posts

Subscribe comments rss Recent Comments

Technorati

Technorati
My authority on technorati
Add this blog to your faves