DO NOT REPLY [Bug 12812] New: - CGI print to STDERR after POST does *not* appear in error_log

[bu...@apache.org]

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=12812>.
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=12812

CGI print to STDERR after POST does *not* appear in error_log

           Summary: CGI print to STDERR after POST does *not* appear in
                    error_log
           Product: Apache httpd-2.0
           Version: 2.0.40
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: hmerrill@redhat.com


After upgrading my machine to Apache 2.0.40 and Perl 5.8.0, my Perl CGI script
is acting funny.  This script does a POST back into itself by *not* specifying
an ACTION.  For debugging, I put a 'print STDERR "Some text\n";' at the top of
my script - the 1st time into this script, that print appears in the Apache
error_log, but after the POST, the print should appear again, but it doesn't.  I
know execution *is* coming back into the same script, because if I remove the
STDERR from the print(so that it is printing to STDOUT), I get the typical "Bad
header" error.

Is this a bug with Apache 2.0?  Using 'print STDERR "blah blah\n";' always
worked for me before this - those prints always appeared in the Apache error_log.

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