Hello,
I have installed and configure squid (ver. 2.4.STABLE4) and using squidGuard
(ver. 1.2.0) as the redirector. Running on the same machine is Apache on port 81.
Listed below is an example squidGuard.conf file:
=========
logdir /usr/local/squidGuard/logs
dbhome /usr/local/squidGuard/db
source myComputer {
ip 123.456.123.456 ## not the actual address
}
acl {
myComputer {
pass none
}
default {
pass none
redirect http://127.0.0.1:81/login.html
}
}
==========
Basically, the idea is that when a HTTP request is received via "myComputer", a
redirection is made to a login page. The user is then required to enter a user id and
password. When the submit button is pressed, the ACTION is on a login.pl script and
the POST method is used to send the details to Apache via Squid and SquidGuard. If
granted access, the "pass none" in myComputer is changed to "pass all".
In reality, after receiving the POST, Apache issues the 405 message, "Method not
allowed. POST is not allowed for the URL/login.html". When the same login page is
accessed directly from Apache (by-passing squid and SquidGuard), the login process
works as expected. Investigation reveals the "redirect" statement in the "default"
section to be the likely cause. Squid correctly receives the POST on login.pl script,
however SquidGuard changes login.pl to login.html and returns the new URL to squid,
which then sends the POST on login.html to Apache.
My questions are:
1) Is the example squidGuard.conf correct?
2) Is squidGuard functioning correctly?
The information contained in this e-mail and any attachments is confidential to Roke
Manor Research Ltd and must not be passed to any third party without permission. This
communication is for information only and shall not create or change any contractual
relationship.
