On Thu, 2003-07-03 at 01:24, Bill Marrs wrote:
This fixed the bug for me.
Great! Will commit it in the near future. (Can't seem to access the cvs server right now, crappy internet cafe)
-1, this is a wrong solution. print ""; should flush just like it did in mod_perl 1.0 if $| == 1; Consider this script:
print "Content-type: text/plain\n\n";
local $| = 0;
print "start\n\n";
local $| = 1;
print "";
sleep 5;
local $| = 0;
print "end\n";print "", must immediately flush the buffered data, since $| has changed from 0 to 1.
One thing that could help is if someone could take the time to write a test for this bug.
Unfortunately I don't seem to be able to reproduce the problem, so I can't debug the problem. It could be a bug on the mod_deflate's behalf as well. Philippe, were you able to reproduce the problem with Bill's setup? I was writing a test, but couldn't get it to fail... may be because i was using 2.0.47. Bill, do you have the problem with the latest apache version?
Also Bill, why do you have this setup:
<Location /perl> AddOutputFilterByType DEFLATE text/* SetOutputFilter DEFLATE </Location>
why adding it twice? You need only the latter inside <Location>, or alternatively only the former outside <Location> if you want it to be set globally:
http://httpd.apache.org/docs-2.0/mod/core.html#addoutputfilterbytype
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
