On May 26, 2011 09:36 Torsten wrote:
>
> Since I haven't heard from you I take it the problem has been resolved,
> has it? Did you try Steve's patch?
>
I have done a lot of testing on many different systems but still haven't
figured it out exactly when the problem occurs. I have found that on
wi
Torsten Förtsch wrote on 2011-05-17:
> On Tuesday, May 10, 2011 21:15:29 Thomas den Braber wrote:
>> In http://www.gossamer-threads.com/lists/modperl/dev/102357 it
>> looks like it is solved.
>
> Thomas, could you please check if the patch at
>
> http://www.gossamer-threads.com/lists/modperl/de
On Tuesday, May 10, 2011 21:15:29 Thomas den Braber wrote:
> In http://www.gossamer-threads.com/lists/modperl/dev/102357 it
> looks like it is solved.
Thomas, could you please check if the patch at
http://www.gossamer-threads.com/lists/modperl/dev/102983#102983
fixes your problem? It sounds qu
On Wednesday, May 11, 2011 17:15:19 Thomas den Braber wrote:
> I think it is better to fix this in Mod Perl than making workaround.
Patches are welcome, really. Currently, we are quite short of Windows
programmers.
Torsten Förtsch
--
Need professional modperl support? Hire me! (http://foertsch
> We were getting this behavior in our web application. It appears that
> we've fixed it (we're still testing it) by checking the return value
> from each print statement (usually we call the Apache request object's
> print method) and aborting (by calling die() in our application - we
> have an
We were getting this behavior in our web application. It appears that we've
fixed it (we're still testing it) by checking the return value from each print
statement (usually we call the Apache request object's print method) and
aborting (by calling die() in our application - we have an all-encom
