Sheridan Posted May 15, 2014 Posted May 15, 2014 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!
penfold_99 Posted May 15, 2014 Posted May 15, 2014 You are still able to get to a non-ssl version by going to Google
Sheridan Posted May 15, 2014 Author Posted May 15, 2014 That works, but the nosslsearch option isn't anymore -which is what smoothwall must have used.
Iain Posted May 15, 2014 Posted May 15, 2014 The nosslsearch.google.com setup is working for us here, although we don't use Smoothwall.
Sheridan Posted May 15, 2014 Author Posted May 15, 2014 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?
robk Posted May 15, 2014 Posted May 15, 2014 Working via smoothwall here, SSL seach disabled and safe search applied.
Sheridan Posted May 15, 2014 Author Posted May 15, 2014 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.
Sheridan Posted May 15, 2014 Author Posted May 15, 2014 Getting more and more weird - even using the DNS trick to redirect google.com and google.co.uk to nosslsearch.google.com doesn't work as it simply redirects to https://www.google.co.uk - even though an nslookup for Google brings up the nossl dns entry I have created!
lcalway Posted May 23, 2014 Posted May 23, 2014 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?
lcalway Posted May 23, 2014 Posted May 23, 2014 We have got it working by removing the "Dot" from the end of "nosslsearch.google.com.". Hope that helps someone out.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now