On Thu, Jul 17, 2014 at 1:25 PM, Moshe Katz wrote:
> On Thu, Jul 17, 2014 at 12:13 PM, Dean Landry
> wrote:
>
>> Thanks Moshe,
>>
>> I've run squidGuard via ssh as suggested and get the correct URL. So
>> it's something other than SquidGuard. I noticed that any new URLs I try
>> seem to be cor
On Thu, Jul 17, 2014 at 12:13 PM, Dean Landry wrote:
> Thanks Moshe,
>
> I've run squidGuard via ssh as suggested and get the correct URL. So it's
> something other than SquidGuard. I noticed that any new URLs I try seem to
> be correctly redirected. Could it be that Squid itself is caching th
Thanks Moshe,
I've run squidGuard via ssh as suggested and get the correct URL. So it's
something other than SquidGuard. I noticed that any new URLs I try seem to
be correctly redirected. Could it be that Squid itself is caching the
response from when my configuration was previously broken?
Th
The first thing you can check is whether the error is being introduced in
SquidGuard itself or later in the stack.
Run "/usr/pbi/squidguard-squid3-amd64/bin/squidGuard -c
/usr/pbi/squidguard-squid3-amd64/etc/squidGuard/squidGuard.conf" in a shell
(console or SSH) and pass those URLs to it to see t
Hello,
We have configured pfSense with Squid3 and SquidGuard in order to do
content filtering. We have blocked several categories and also have a set
of manually blocked URLs. If I attempt to go to a manually blocked URL, I
am correctly redirected to the sgerror page:
https://10.10.10.1/sgerror
