forceGoogleSafeSearch only works for transparent proxy?

[GoogleCodeExporter]

Unless I'm doing something wrong (and I'd love if you pointed it out!), 
forceGoogleSafeSearch seems to work only if I set a transparent proxy (no 
matter if using filterworkmode 0 or 1). 

When I configure the web browser (I tested with Firefox 8 and Midori 2.4) to 
use the proxy explicitly, all other filtering works, but not 
forceGoogleSafeSearch. Maybe the browser doesn't allow us to modify the 
headers? I don't know...

Could you shed some light? Do you confirm this is a bug? I uploaded some 
improvements for SafeSearch but I can't figure out this one..!

Thank you and best regards, 
Teresa e Junior

Original issue reported on code.google.com by teresaejunior on 5 Dec 2011 at 10:31

[GoogleCodeExporter]

That's right, We will work on it as soon as possible.

Best regards and thanks.

Original comment by mind....@gmail.com on 8 Dec 2011 at 1:31

• Changed state: Accepted
• Added labels: Milestone-Release1.2

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Maybe it would be easier to write a good regex for urlregexplist or 
headerregexplist? Also because the current forceGoogleSafeSearch allows the 
user to bypass it by adding some slashes, for example: 
http://www.google.com.br//////search?q=badword. The slashes could be handled 
with the regex too.

Original comment by teresaejunior on 8 Dec 2011 at 2:01

[GoogleCodeExporter]

Ok but Comment 3 is another issue, I will create it separately when I start to 
fix it.

Original comment by mind....@gmail.com on 2 Apr 2012 at 6:14

[GoogleCodeExporter]

OK, thanks! I just meant if it would not be easier to have the regexes, which 
also work on transparent proxy, instead of hardcoding the SafeSearch in C++... 
just an idea.

Original comment by teresaejunior on 2 Apr 2012 at 8:31