On Fri, Jan 17, 2003 at 04:36:58PM +1100, Stas Bekman wrote:
Consider this mod_cgi script:
#!/usr/bin/perl -w
print Content-type: text/plain\n\n;
print no_such_func();
print Shouldn't be printed;
httpd.conf:
ScriptAlias /cgi-bin/ /home/httpd/2.0/perl/
The error is correctly logged:
-
From: Stas Bekman [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 11:37 PM
To: [EMAIL PROTECTED]
Subject: bug in mod_cgi (sends 200 instead of 500)
Consider this mod_cgi script:
#!/usr/bin/perl -w
print Content-type: text/plain\n\n;
print no_such_func();
print Shouldn't
Justin Erenkrantz wrote:
--On Friday, January 17, 2003 4:36 PM +1100 Stas Bekman
[EMAIL PROTECTED] wrote:
Consider this mod_cgi script:
# !/usr/bin/perl -w
print Content-type: text/plain\n\n;
print no_such_func();
print Shouldn't be printed;
httpd.conf:
ScriptAlias /cgi-bin/
* Stas Bekman wrote:
It shows that I haven't run mod_cgi for ages. I was just used to having
this as a failure (500) under mod_perl. Any reason for not checking the
return status?
hmm, performance? memory usage? What about a script that throws out a lot
of data (say, 1 MB, multiplied with
* 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
Consider this mod_cgi script:
#!/usr/bin/perl -w
print Content-type: text/plain\n\n;
print no_such_func();
print Shouldn't be printed;
httpd.conf:
ScriptAlias /cgi-bin/ /home/httpd/2.0/perl/
The error is correctly logged:
[Fri Jan 17 16:31:03 2003] [error] [client 127.0.0.1] Undefined
