On Thursday 12 September 2013 at 18:03:52, Paul Cieslar wrote:
> Hi All.
>
> I am running Squid 3.3 behind a Draytek firewall. The firewall has Web
> Content Filtering configured, which delivers a custom page when
> unauthorised content is requested. Both work fine separately (and
> together in most cases), however when trying to access unauthorised
> content through Squid, an empty document is returned to the browser,
> instead of the error message from the Draytek. We can't roll out squid to
> everyone if it will deliver blank pages instead of the error information
> as it will become a support headache.
>
> Does anyone know of a way around this?
Can you do a packet capture (eg: with wireshark) on the interface between
Squid and the Draytek, to see if there's some discrepancy between source and
destination IP addresses of the request and the response, or something
similar, which would upset Squid?
What do you see in Squid's logs when you attempt to access unauthorised
content and shoould see the Draytek message?
Does the Draytek allow you to modify the page returned?
Regards,
Antony.
--
The lottery is a tax for people who can't do maths.
Please reply to the list;
please don't CC me.
