Squid 3 / Squidguard still blocks sites even after removal/issues with blocking
-
Okay so I am getting a rather odd experience with squidguard, it blocked sites fine and I could make changes fine, then suddenly as I removed youtube (as a test) it still was blocking youtube even though the site wasnt in the targetlists… And then I removed squid and squidguard and still youtube is blocked?
EDIT: So I found the culprit it was a file under /usr/pbi/squidguard-squid3-i386/etc/squidGuard/ called "squidGuard_usrdbrebuild.conf" which was blocking "blocked sites" where ever they were being defined I dont know :S can anyone help?
-
Are you sure it's that?
I have found that using Chrome, Chrome caches the redirect so that even with no proxy it remembers that it should be forwarded to the error page, which it usually has cached too.
Clearing the cache should get it back. Using Incognito/Private Window mode as a test to avoid the cache is also helpful.
-
Are you sure it's that?
I have found that using Chrome, Chrome caches the redirect so that even with no proxy it remembers that it should be forwarded to the error page, which it usually has cached too.
Clearing the cache should get it back. Using Incognito/Private Window mode as a test to avoid the cache is also helpful.
Yep I tried every browser going, and also tried Ctrl + F5 and clearing the cache :P. I edited that file however and it worked.
-
Are you sure it's that?
I have found that using Chrome, Chrome caches the redirect so that even with no proxy it remembers that it should be forwarded to the error page, which it usually has cached too.
Clearing the cache should get it back. Using Incognito/Private Window mode as a test to avoid the cache is also helpful.
Jimp did you ever manage to find out what the issue is and how to get browsers not to cache the denied pages? I have a time system here and modifying a file before lunch everyday so people can browse their facebook is not going to help me much?
Thanks!!
-
For redirects, use "External URL Found" and redirect it to your own error page. The client browser is less likely to (but still can) cache a 302.
