Re: [Mason] error_format

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Dave Rolsky writes:
 > On Fri, 6 Dec 2002, Kwindla Hultman Kramer wrote:
 > 
 > > Is it possible for "$req->error_mode('foo')" to work this way as well?
 > 
 > It should work.  It's a settable property of the Request object.
 > 
 > > my $remote_ip = $r->get_remote_host();
 > > my $req = $ah->prepare_request ( $r );
 > > return $req unless  ref($req);
 > > $req->error_mode ( $err_modes{$remote_ip} ) if $err_modes{$remote_ip};
 > > $req->exec();
 > >
 > > But that doesn't work. Switching from a constructor-set default
 > > 'output' mode to 'fatal' mode causes requests that have errors to
 > > return no data, or a few blank lines. No error line ends up in the log
 > > file, and the Apache ErrorDocument handling doesn't get triggered.
 > 
 > You'll also have to switch the error_format at the same time, I think.
 > 'html' format and 'fatal' mode seem to not cooperate.  I haven't
 > investigated this too much since I don't see the point of sending HTML
 > pages to the Apache error log ;)
 > 

Ah hah -- that was the piece I had missed. Adding one line to the test
component shows that things do, indeed, work as promised:

# ----

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html><head>
<title>test error mode change</title>
</head>
<body>

<% $m->error_mode('fatal') %>
<% $m->error_format('line') %>

% die;

</body>
</html>