>Number: 5070 >Category: os-next >Synopsis: Full output of CGI scripts not flushed. >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Sep 27 15:50:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 & 1.3.9 >Environment: Hardware: HP PA-RISC OS: NextStep 3.2 C: GNU C >Description: Sometimes (seemingly randomly) the full output of a CGI script (PERL) is not getting sent to the browser. If I run the script directly on the server everything works correctly. I have tried resetting the $| (buffer) special variable in PERL (setting to non-zero makes things worse).
It seems more likely to occur if the CGI script called by the browser itself calls other scripts, but even a simple script can cause the problem. This problem did not exist in release 1.3.4. >How-To-Repeat: I have currently regressed back to apache 1.3.4 which fixes the problem. >Fix: Take a look at what changed between 1.3.4 and 1.3.6 >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
