mahashakti89 wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi !
After setting up dspam as a content filter, it works now O.K, I am
trying to set up the webfrontend, but ....
if I turn my browser to https://localhost/dspam/html/dspam.cgi , I am
prompted for a username and a password ... Seems quite natural
I tried it with User root and Password xxxx, but it doesn't work ... I
am not familiar with apache and servers, I am on a standalone machine
with a RTC connection . I think something is wrong with my httpd.conf ...
Could need some help.
I added this section from a Debian specific Howto in my httpd.conf :
<Directory "/var/www/dspam/html">
Options FollowSymLinks ExecCGI
AllowOverride None
Order deny,allow
Deny from all
AddHandler cgi-script .cgi .pl
SSLRequireSSL
AuthType Basic
AuthName "DSPAM Control Center"
AuthUserFile /var/www/dspam/etc/htpasswd
Require valid-user
Satisfy Any
</Directory>
mahashakti89
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF7rqbI8R+aqI0N8ERAtlcAKCU3G7BPzO4rygLSL21RJ+AS0hcpACfQSpT
rLOo7AJv2QqmPaQLkrLXsaY=
=UzTW
-----END PGP SIGNATURE-----
The WebUI needs to know who's data to display, so you setup an
authentication mechanism in Apache to do so. Apache (mod_auth_mysql,
.htaccess, etc) verifys the username and password, from the prompt, and
dspam then loads data for said authenticated user.
Basically, the prompt is used by dspam (though not from dspam) to figure
out who is logging in, so that it can load the correct user data.
Hope this helps?
Kyle
