You are still able to get to a non-ssl version by going to Google
I know google forced all searchs to SSL, but has that option gone now? You used to be able to use nosslsearch.google.com, but that redirects to SSL. Made a mess of our smoothwall if we enabled the nosslsearch option (although it was classed as BETA it used to work)
Not too bothered - as we'll leave ssl searches in google enabled, just curious!
That works, but the nosslsearch option isn't anymore -which is what smoothwall must have used.
The nosslsearch.google.com setup is working for us here, although we don't use Smoothwall.
If you enabled the EnableGoogleNoSSLSearch option here on our smoothwall - it breaks google, you just get a strange error about the ssl proxy. It used to work, but stopped today so I wonder if google have changed something and smoothwall doesn't like it anymore?
Working via smoothwall here, SSL seach disabled and safe search applied.
We have safe search enabled, and until today also had the ssl search disabled. Then it started to generate ssl/certificat errors, althought the errors varied from browser to browser. IE simply said you need to enable TLS, Chrome said the ssl certificate was 'too long' (!) and firefox also complained about the certificate being incorrect. All the PCs have the guardian on as a CA installed via group policy so I don't know why its suddenly changed.
We have also created the DNS entries and get the NSLookup to return nosslserch.google.com, but like Sheridan when browsing it goes to https://www.google.com.au. Has anyone found a solution to this yet?
We have got it working by removing the "Dot" from the end of "nosslsearch.google.com.". Hope that helps someone out.
There are currently 1 users browsing this thread. (0 members and 1 guests)