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 11178] New: - mod_cgi and mod_cgid do not handle buffer flushing well
Date Thu, 25 Jul 2002 18:37:07 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=11178>.
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=11178

mod_cgi and mod_cgid do not handle buffer flushing well

           Summary: mod_cgi and mod_cgid do not handle buffer flushing well
           Product: Apache httpd-2.0
           Version: 2.0.39
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: mod_cgi
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: josmhinkle@netscape.net


These are points not yet seen in the few bug reports on this subject.

mod_cgid does not seem to flush buffers until the CGI program ends, and mod_cgi 
follows some unhelpful rules in flushing buffers.  This strongly affects tabular 
data sent from cgi programs.  mod_cgi seems to flush buffers when an HTML <BR> 
line break is detected, but not necessarily a line terminator "\n", and possibly 
when the character count reaches 80.  A <BR> character is not the only display 
line ending, so are </TR> in a table, and </LI> in list items.  It would be very

much better if the module only detected control characters, which are not 
displayed in a page, and did not depend on page content to determine 
transmission controls.

The effects are such that nothing is displayed in a browser until a complete 
page is generated by a CGI program, meaning the user cannot see pushed material 
until his session ends.  

mod_cgi and mod_cgid should display the same behaviours regarding data handling. 
 Their difference is in threading, not as alternate page display methods.  To 
have them dissimilar would force a good deal of software to become utterly 
unportable.  Already I have had to derive 3 versions of some CGI programs to 
allow them to work (hopefully) on mod_cgi, mod_cgid, and Apache 1.3.  One has 
not been portable at all to mod_cgid so far.

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


Mime
View raw message