RE: RE: RE: error document

2007-07-09 Thread Gerald Richter - ECOS GmbH
> > I ran the tests, and the result is as follows. > That sounds ok. In this case could you please run your httpd under gdb with the -X option e.g. gdb --args /path/to/httpd -f /path/to/httpd.conf -X Then do the request where you get the bus error and at the gdb prompt type bt And send

RE: RE: error document

2007-07-06 Thread Ben Kim
I ran the tests, and the result is as follows. Both test will fail, but when you look at test/tmp/out.htm after each test, you should see the sentence "This page is shown due to an ErrorDocument redirection". make test TESTARGS="-h errdoc/errdoc.htm" Same as test/cmp/errdoc.htm This page

RE: RE: error document

2007-06-29 Thread Gerald Richter - ECOS GmbH
> > I ran httpd on another port with -X, and it's somewhat interesting. > > When the first request to the httpd (started with -X) is for > a missing page or a page with error, I get bus error or > segmentation fault and apache dies. > > If the first request is a hit and successful, subsequent

RE: RE: error document

2007-06-14 Thread Gerald Richter - ECOS GmbH
Hi, > > I ran httpd on another port with -X, and it's somewhat interesting. > > When the first request to the httpd (started with -X) is for > a missing page or a page with error, I get bus error or > segmentation fault and apache dies. > > If the first request is a hit and successful, subseq

RE: error document

2007-06-08 Thread Ben Kim
I guess the problem might happen when the same child serves the page again, so the initialisation is skiped. Could you try to run httpd with the -X option, so you have only one process. Does it now fail the second request? I ran httpd on another port with -X, and it's somewhat interesting.

RE: error document

2007-06-06 Thread Gerald Richter - ECOS GmbH
sday, May 31, 2007 12:34 PM > To: [email protected] > Subject: error document > > > Hi, > > I reported a related problem once but didn't get a good > answer last time... I thought I'd try again. > > We are on > Apache/2.2.4 Embperl 2.2.0 mod_p

error document

2007-05-31 Thread Ben Kim
Hi, I reported a related problem once but didn't get a good answer last time... I thought I'd try again. We are on Apache/2.2.4 Embperl 2.2.0 mod_perl/2.0.3 but not using Embperl Objects. I'm trying to solve the problem of 500 errors not showing custom error document, afte

Re: error document continues

2002-11-12 Thread Gerald Richter
://www.ecos.de Fax: +49 6133 925152 - - Original Message - From: "Jordan Baker" <[EMAIL PROTECTED]> To: "'embperl'" <[EMAIL PROTECTED]> Sent: Tuesday, November 12, 2002 12:27 AM Sub

error document continues

2002-11-11 Thread Jordan Baker
below for optReturnErrors Any help would be appreciated... __ Jordan Baker [EMAIL PROTECTED]  -Original Message- From: Jordan Baker [mailto:sutra@;rogers.com] Sent: November 7, 2002 6:48 PM To: 'embperl' Subject: error document I'm trying to use Apache/mod_perl

error document

2002-11-07 Thread Jordan Baker
I'm trying to use Apache/mod_perl and ErrorDocument. With what I have right now if I try to execute the script I see the contents of my base.epl but neither the file I called (which has deliberate syntax errors in it) or the servererror.epl file. Currently I've got: ErrorDocument 500 /servererro

Re: How can I trigger an error document from HTML::EmbperlObject?

2002-06-25 Thread Gerald Richter
rch engines, which I would prefer to do. > $status = Execute({inputfile => '*', options => HTML::Embperl::optReturnError, errors => \@errors}); @errors will contain all error messages, if there are any You could also set the optReturnError in your httpd.conf in EMBPERL_OPTIONS

How can I trigger an error document from HTML::EmbperlObject?

2002-06-20 Thread Kee Hinckley
I want something like: $status = Execute({inputfile => '*'}); if ($status) { where if there's an error I go to my default /error.html file, which can then print out all the information I'd normally get using the ErrorDocument directive. Barring that an internal redirect would