http://www.google.com/?nord=1 not working

[thiefware]

[google.com...] (non-https connection) is not working anymore. It gets redirected to: [google.com...] (secured connection). Is there a way to get unsecured search results?

[keyplyr]

I wouldn't think so.

[lammert]

Phasing out the http version of Google Search seems in line with the tightening of Google's overall security including not allowing Diffie-Hellmann keys and SHA1 hashes on SSL certificates in their Chrome browser. Recently they also forced some of their other products including Google Map Maker to https.

Expect Google's encryption settings to be even more tightened in the future.

If you are relying on http connections for non-human Google Search access like scraping, this is the time to make your tools https proof.

[thiefware]

I was hoping there was a way to search without https. Http pages are faster to access.

[thiefware]

When did http://www.google.com/?nord=1 stop working? Anyone know when that option went away? It just seemed like it went away without notice until I paid more attention to what was happening to the [http] turning into [https].

[bumpski]

In the thread below I did several detailed tests of Google's home page with and without https so I know in late March it was still working.
[webmasterworld.com...]
At that time I found the http: would have loaded in 1.4 seconds, while the https version took 2.9 seconds to load.
Google doesn't want you to do an insecure search because it allows all the intermediaries to sniff the key words you are searching for. They should just give people a choice!
Even the http version using the nord option did do one https request.
But I think it must have been fairly recent change, July sometime?.
Amazon very recently changed to https. I have been bantering with [e-mail] regarding how slow Amazon has become. I also passed on the fact that their home page has 3 meg of images when you're logged out and 8 meg when you're logged in, and now they loaded https on top of that.
Google's home page has grown from 5K to 518K since 2008, almost as much as college tuitions! And forcing https more than double's the load time.
I'll bet the phone cell phone companies love it! Thousands of extra padding bytes!
This link discusses the problems and hints that Google does have some optimizations.
[igvita.com...]

[thiefware]

thanks bumpski for the extensive review of google. From 5K to 518K for google page size—Wow! 100x larger. Talk about bloated pages! Wowzers!