httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18348] New: - Errorlogging / STDERR from nph-cgi-scripts broken
Date Tue, 25 Mar 2003 22:46:18 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18348>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18348

Errorlogging / STDERR from nph-cgi-scripts broken

           Summary: Errorlogging / STDERR from nph-cgi-scripts broken
           Product: Apache httpd-2.0
           Version: 2.0.43
          Platform: All
        OS/Version: FreeBSD
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_cgi
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: info@orangexl.com


Non parsed header scripts are not able to log any errors or warnings to the 
errorlog, while (almost) the same non-nph script will generate errors and 
warnings for the same script.

example:


#!/usr/bin/perl -w
use strict;
$|=1;
warn "me";
print "$ENV{SERVER_PROTOCOL} 204 No Content\n";
print "Server: $ENV{SERVER_SOFTWARE}\n";
print "Date: $date\n";
exit;

will not log anything, while it should due to the warn in line 4.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message