Re: [MP2 - BUG ?] Issue handing Apache config. error messages

Issac Goldstand wrote: [...] (Starting with mor_perl 2)... I'm toying with the idea of starting the porting tutorial, but I want to make sure it's written well for clueless people (which I probably still at least half count as :-)) and with accurate content. porting or starting? We already have a

Re: [MP2 - BUG ?] Issue handing Apache config. error messages

- Original Message - From: "Stas Bekman" <[EMAIL PROTECTED]> To: "Issac Goldstand" <[EMAIL PROTECTED]> > Issac Goldstand wrote: > > Looking at it now, I tend to agree... I just have a vague recollection of > > my first mod_perl 2 handler (Written only 2 weeks ago, though I dabbled with

Re: [MP2 - BUG ?] Issue handing Apache config. error messages

Issac Goldstand wrote: Right. Could you possibly clarify the difference between SetHandler perl-script and SetHandler modperl? I'm still not sure I've got the straight of it yet... You must be kidding ;) Have you read the sections at the URL posted below? Stas Bekman wrote: Sreeji K Das wrote:

Re: [MP2 - BUG ?] Issue handing Apache config. error messages

Right. Could you possibly clarify the difference between SetHandler perl-script and SetHandler modperl? I'm still not sure I've got the straight of it yet... Issac Stas Bekman wrote: > Sreeji K Das wrote: > [...] > You need to use 'SetHandler perl-script' for that, see: > http://perl.apache.

[MP2 - BUG ?] Issue handing Apache config. error messages

Following demonstrates the problem: $ cat /tmp/test.conf @Include = "/tmp/test1.conf"; Listen 43499 $ cat /tmp/test1.conf $Port = 42480; $ httpd -X -f /tmp/test.conf Syntax error on line 7 of /tmp/test.conf: Use of uninitialized value in subroutine entry at /tmp/CVS/virgin/modperl-2.0/blib

Re: Error messages in Apache::Registry

On 17 Sep 2002 at 13:27, Perrin Harkins wrote: > Matt wrote some stuff for the guide explaining why the die handler is not > the best approach. Basically, it means all errors will be treated the > same. Ahh, right. Is this what you're referring to?

Re: Error messages in Apache::Registry

William McKee wrote: >>The way that most people would recommend in A::R or anything else is to >>trap errors with eval blocks and then handle them appropriately. > > I thought I was doing that at a global level by throwing an error with > die() that was caught by CGI::Carp. I'm realizing that it

Re: Error messages in Apache::Registry

On 16 Sep 2002 at 18:10, Perrin Harkins wrote: > The way that most people would recommend in A::R or anything else is to > trap errors with eval blocks and then handle them appropriately. I thought I was doing that at a global level by throwing an error with die() that was caught by CGI::Carp. I

Error messages in Apache::Registry

Hi folks, I'm a new user to mod_perl. I'm using Apache::Registry to run some scripts that have been written using the CGI::Application framework. Previously, under mod_cgi, I've been using the CGI::Carp set_message method of capturing a die and returning a customized error message to the scree

Re: Error messages for VirtualHosts written to wrong log

Michael E. Lewis wrote: > I sure hope I'm not asking a stupid question here. We are > preparing to upgrade our production mod_perl servers: > From: To: > > RedHat 6.2 RedHat 7.2 > kernel-2.2.19-6.2.7 kernel-2.4.9-31 > Apache_1.3.12 Apache_1.3.23 >

Error messages for VirtualHosts written to wrong log

I sure hope I'm not asking a stupid question here. We are preparing to upgrade our production mod_perl servers: From: To: RedHat 6.2 RedHat 7.2 kernel-2.2.19-6.2.7 kernel-2.4.9-31 Apache_1.3.12 Apache_1.3.23 mod_perl-1.24 mod_perl-1.26 I ha

Re: anyone know a trick with displaying 401 error messages for top level protected sites?

Works fantasticaly! thanks so much. DJ - Original Message - From: "Rob Bloodgood" <[EMAIL PROTECTED]> To: "DJ (David J Radunz)" <[EMAIL PROTECTED]> Cc: "mod_perl" <[EMAIL PROTECTED]> Sent: Wednesday, December 12, 2001 6:09 AM Subject: R

RE: anyone know a trick with displaying 401 error messages for top level protected sites?

> for example if the protected url was http://www.site.com/ the user > would be redirected to http://www.site.com/error/401 for the error > message.. and because its protected wouldnt display the custom error > page instead displaying the following error "Additionally, a 401 > Authorization Requi

RE: anyone know a trick with displaying 401 error messages for top level protected sites?

riginal Message- From: DJ (David J Radunz) Sent: Mon 12/10/2001 22:36 To: [EMAIL PROTECTED] Cc: Subject: anyone know a trick with displaying 401 error messages for top level protected sites? Greetings,

anyone know a trick with displaying 401 error messages for top level protected sites?

Greetings, Ive written a module to hanlde error messages, it works fine except when its used to handle a top level authentication.. and then it doesnt display the page. for example if the protected url was http://www.site.com/ the user would be redirected to http://www.site.com/error/401

Re: error messages..

You're exposing your username/password you're using to connect to your DBMS to public. Those messages are there because $Apache::DBI::DEBUG is set. Rgds, Edwin. Sam Park wrote: > > Anybody knows why I'm getting this messages...??? > 5744 Pinging 'prodcrank.excite.com~crank~crank~RaiseError=1'

error messages..

Anybody knows why I'm getting this messages...??? 5744 Pinging 'prodcrank.excite.com~crank~crank~RaiseError=1' 5744 Apache::DBI already connected to 'prodcrank.excite.com~crank~crank~RaiseErr or=1' 5744 Pinging 'prodcrank.excite.com~crank~crank~RaiseError=1' 5744 Apache::DBI already connected to '