Well, apparently one of more of the changes in the new Apache 3.0
cgi doesn't sit well with squidGuard.cgi.  (squidGuard-simple.cgi
works a little better, btw)

I read through the Apache change log and the upgrading to 3.0
document, but I wasn't able to find the problem. (It doesn't help that
I don't know perl <big grin>)

If anybody has figured out what needs to change in squidGuard.cgi 
for Apache 3.0, please share that information here.

Thanks,
Rick


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of SSCR Internet
> Admin
> Sent: Wednesday, February 26, 2003 10:35 AM
> To: Rick Matthews
> Cc: [EMAIL PROTECTED] Org
> Subject: RE: squidguard.cgi
> 
> 
> Oh, that would be a redhat 8.0 just like yours, and im running squidguard on
> the other box and the squidguard.cgi on the other box (website)
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Rick
> Matthews
> Sent: Monday, February 24, 2003 11:23 AM
> To: SSCR Internet Admin
> Cc: [EMAIL PROTECTED] Org
> Subject: RE: squidguard.cgi
> 
> 
> Actually I was wondering what distribution and version of Linux you
> are running.  Here's why I am asking...
> 
> The squidGuard.cgi that comes with squidGuaurd worked for me once I
> figured out how to get cgi working properly.  I did make a couple of
> changes to squidGuard.cgi but they were cosmetic, so I don't think
> shipping you a copy of mine is going to help you.
> 
> So I would suspect misconfigured cgi, except for what I experienced
> over the weekend.
> 
> I want to off-load some of the work from my squid box and I was
> bringing up Apache on a new Red Hat 8.0 box.  Everything went as
> smoothly as I was hoping until I tried to run the squidGuard.cgi.
> Even after I had corrected all of my errors I'm still unable to
> run squidGuard.cgi.  (I haven't given up, just ran out of time.)
> 
> So, before sending you off in one direction I thought I'd ask what
> you are running, on the remote change that it's not my problem.
> 
> Rick
> 
> 
> > -----Original Message-----
> > From: SSCR Internet Admin [mailto:[EMAIL PROTECTED]
> > Sent: Monday, February 24, 2003 7:41 PM
> > To: Rick Matthews
> > Subject: RE: squidguard.cgi
> >
> >
> > Its squidguard-1.2.0
> >
> > -----Original Message-----
> > From: Rick Matthews [mailto:[EMAIL PROTECTED]
> > Sent: Monday, February 24, 2003 1:09 AM
> > To: SSCR Internet Admin
> > Subject: RE: squidguard.cgi
> >
> >
> > What distribution/version are you running?
> >
> > Rick
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] Behalf Of SSCR
> > > Internet Admin
> > > Sent: Monday, February 24, 2003 6:14 PM
> > > To: Squidguard Mailing List
> > > Subject: squidguard.cgi
> > >
> > >
> > > Do you have any squidguard.cgi that you can share with me? it seems that
> > the
> > > script that comes with the installation wont work for me..
> > > ---
> > > Outgoing mail is certified Virus Free.
> > > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > Version: 6.0.456 / Virus Database: 256 - Release Date: 2/18/2003
> > >
> > >
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.456 / Virus Database: 256 - Release Date: 2/18/2003
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.456 / Virus Database: 256 - Release Date: 2/18/2003
> >
> >
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.456 / Virus Database: 256 - Release Date: 2/18/2003
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.456 / Virus Database: 256 - Release Date: 2/18/2003
> 
> 

Reply via email to