httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Malo ...@perlig.de>
Subject Re: bug in mod_cgi (sends 200 instead of 500)
Date Sat, 18 Jan 2003 02:02:09 GMT
* Stas Bekman wrote:

> What I was missing is the error message attached to the end of the normal
> output to indicate that there was a problem (better late than never).
> 
> e.g. the following script:
> 
> #!/usr/bin/perl -w
> print "Content-type: text/plain\n\n";
> print "Should be printed";
> print no_such_func();
> print "Shouldn't be printed";

Well, that can be easily decided by the developer:
(it's not exactly the same, but does the trick in nearly all cases)

#!/usr/bin/perl -w
use CGI::Carp 'fatalsToBrowser';
print "Content-type: text/plain\n\n";
print "Should be printed";
print no_such_func();
print "Shouldn't be printed";

:-)

nd
-- 
$_=q?tvc!uif)%*|#Bopuifs!A`#~tvc!Xibu)%*|qsjou#Kvtu!A`#~tvc!KBQI!)*|~
tvc!ifmm)%*|#Qfsm!A`#~tvc!jt)%*|(Ibdlfs(~  # What the hell is JAPH? ;
@_=split/\s\s+#/;$_=(join''=>map{chr(ord(  #             André Malo ;
$_)-1)}split//=>$_[0]).$_[1];s s.*s$_see;  #  http://www.perlig.de/ ;

Mime
View raw message