It's not a CGI thing - it's the charset that CGI adds.
print "Content-type: text/plain;\r\n\r\n";
and
print "Content-type: text/plain; charset=ISO-8859-1\r\n\r\n";
give different results - no matter which of shell, perl, with or without CGI is involved. For the latter, the browser seems to gather all its input first read in blocks, presumably to apply conversions on the complete text to each. (tested with Firefox only).
Try appending "\0" x 1024 to each line using CGI with print $cgi->header("text/plain").
Another way to confirm that unbuffered IO is turned on with CGI is snarfing the packets with eg wireshark.
...another update: even the trailing ; after text/plain makes a difference. If you are not outputting that, the browser buffers.
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|