--- Lee Carmichael <suppressed> wrote:
> Hello Everyone,
>
> I need to capture exceptions caused in the cgiapp_prerun sub. In my situation, I want to verify
> a set of environmental parts that are used in many run modes. So instead of verifying these each
> time, I would like to do it in the prerun and then output a nice universal error page (one used
> for other errors).
>
> Taking the advice from a previous discussion:
> http://www.nabble.com/error-mode-question-tf2025600.html#a5580234, I took the time to add test
> cases and write a patch but I did so on CGI-Application-4.07_01 source. There are two problems
> with 4.07: it is much slower than 4.06 and has a large set of dependencies.
>
just curious. why are you using the Dev version of CGI-Application-4.07_01? it doesn't seem to
have any advantages to me.
regarding trapping errors, usually the failures from cgiapp_prerun/setup are unexpected system
errors. I let apache handle that (use ErrorDocument)
James.
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.