Fw: Re: Re: Re: [us...@httpd] 500 internal server error running php application

2010-09-03 Thread J Wilson
ation. # If you are running into such problems, simply remove the # from the beginning of the following lines: #SecFilterEngine off #SecFilterScanPOST Off ~ ~ ~ ~ ~ --- On Fri, 9/3/10, J Wilson wrote: > From: J Wilson > Subject: Re: Re: Re: [us...@httpd] 500 internal server error running ph

Re: Re: Re: [us...@httpd] 500 internal server error running php application

2010-09-03 Thread J Wilson
w,Deny Allow from all IndexIgnore */* ~ ~ ~ ~ ~ --- On Fri, 9/3/10, ja...@nixsecurity.org wrote: > From: ja...@nixsecurity.org > Subject: Re: Re: Re: [us...@httpd] 500 internal server error running php > application > To: users@httpd.apache.org > Date: Friday, September 3, 201

Re: Re: Re: [us...@httpd] 500 internal server error running php application

2010-09-03 Thread james
Could you possibly paste the contents of the .htaccess file? > Original Message >From: J Wilson >To: users@httpd.apache.org >Sent: Fri, Sep 3, 2010, 11:47 AM >Subject: Re: Re: [us...@httpd] 500 internal server error running php >application > >Error Log: >

Re: Re: [us...@httpd] 500 internal server error running php application

2010-09-03 Thread J Wilson
/catalog/ --- On Fri, 9/3/10, ja...@nixsecurity.org wrote: > From: ja...@nixsecurity.org > Subject: Re: Re: [us...@httpd] 500 internal server error running php > application > To: users@httpd.apache.org > Date: Friday, September 3, 2010, 9:39 AM > I'd also ta

Re: Re: [us...@httpd] 500 internal server error running php application

2010-09-03 Thread james
I'd also take a look at the Apache error_log to see if there's any indication evident there. Keep in mind that if the PHP code suppresses error reporting (by prefixing expressions with the @ character) then nothing will be reported. > Original Message >From: Eric Covener >To: users@htt