google keeps reverting to httpS

[CMilwright]

I just downloaded Camino 2.1.2 yesterday. I have the quick search box in the top right corner, to the right of the address bar; and my default search engine is google. Whenever I enter anything in the search box, no matter if I've been on a secure or non secure site, the google results page comes up with an https address, not http. If I override it to http, the next time I go back to the search results it changes it to secure again. Where is the preference to stop this from happening, so that my search results page is plain http again like it was with my previous version?

[Andrew`]

This is not a browser setting. Google is automatically redirecting searches to use SSL/TLS.

If you prefer http:// you could try DuckDuckGo - they don't seem to redirect searches to SSL.

[phiw13]

Where is the preference to stop this from happening, so that my search results page is plain http again like it was with my previous version?

There is no preference. https is the default for google search; this has been the case for all Camino 2.1 versions. It guarantees more privacy and security. What is not to like?

If you absolutely want to have your searches go over http, then you'll have to make a bookmark for google with keyword (sees docs).

[CMilwright]

I hate it. The old version didn't default to this. Now every time I use the forward and back buttons from a search result, I get the "entering a secure page" or "exiting a secure page" warnings. **Don't bother to suggest that it's as simple as turning off those warnings, I want them there for other reasons, but not for googling!!
Also 2.1 is very buggy. I only downloaded it this week and it's already "not responded" till I forced it quit about 6 different times. And for the first time ever since I owned my iMac it had an error when it booted up this morning. That could be a coincidence, but it's a suspicious one.

[RPMozley]

Well for Google, you could set their preferences to open link in a new window/tab. So going back to the results page will not get the warnings, as it's already there in a different tab or window.