You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Ullrich von Bassewitz <uz...@musoftware.de> on 1998/11/14 20:25:24 UTC

os-windows/3402: CGI output is always buffered

>Number:         3402
>Category:       os-windows
>Synopsis:       CGI output is always buffered
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Nov 14 11:30:00 PST 1998
>Last-Modified:
>Originator:     uz@musoftware.de
>Organization:
apache
>Release:        1.3.3
>Environment:
Windows NT 4.0 German with SP 3 installed, ActivePerl build 506
>Description:
Under NT, the output of Perl CGI scripts is always buffered. The problem does exist with nph- scripts and with other scripts. Some tests (piping the script output into a file) show that the problem is not caused by the script itself or by the Perl interpreter. In addition, the same scripts work without problems (that is, with unbuffered output) when running them under Linux 2.0.35 with Apache 1.2.5 (as nph- scripts). So the problem seems to be specific to the Apache implementation running on the Windows platform.
>How-To-Repeat:
Since the NT server is not connected to the internet, it�s difficult to give an example URL. Just write a little Perl CGI that outputs one line at a time and connect with a browser. Without buffering, your browser should display one line after the other, and this is indeed what�s happening when running such a script under Linux. When running the same script under NT you will get the output in big chunks (many K).
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]