Henrik,
Thanks for this idea, but unfortunately the vital element is still missing.
The point was that under Squid 1, the redirected URL ended up in the logs,
permanently recording "User X tried to access this porn site and was
blocked".
Under Squid 2, the URL appears before redirection, simply recording "User X
accessed this porn site". The same occurs using "302" browser redirection.
My proxies handle a fair bit of traffic each day, and my clients like the
kind of daily report I can generate by doing a "grep page_denied access.log
> report.txt". Obviously I can't do this if I only get the pre-redirected
URL. Plus, the evidential value of the logs in disciplinary hearings (we
sack people for browsing porn!) is diminished horribly.
Is there any way I can get the old level of logging detail around
redirection back, or am I looking at a reversion to Squid 1.1.22?
I appreciate your assistance.
Richard Stagg
[EMAIL PROTECTED] on 23/12/98 00:37:32
To: Richard Stagg/TMU/CSC
cc: [EMAIL PROTECTED]
Subject: Re: Squid 2 and logging
[EMAIL PROTECTED] wrote:
> A small difference in the logging strikes me: I have a redirector dealing
> with "unsuitable" browsing. For example, "http://www.playboy.com" is
> redirected to "http://my-web-server/page_denied.pl?http://www.playboy.com
"
On this kind of redirects you should use a browser redirect. Change your
redirector to return
302:http://my-web-server/page_denied.pl?http://www.playboy.com which
tells Squid to redirect the browser to
http://my-web-server/page_denied.pl?http://www.playboy.com
---
Henrik Nordstrom
Spare time Squid hacker
