Jeff Finn wrote:
Except Stas is not getting the error when he tries it... hmm.
I'm going to check it again tonight, and I'll include the error
log output. I'm also going to try to use the eval statement he
suggested in the test, but I'm not sure that it will be practical
for me in my application.
2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: RE: ModPerl::Registry: Software caused connection abort
>From: "Jeff Finn" <[EMAIL PROTECTED]>
>Ok; I have generated a semi-self-contained Apache-test that will produce
>this error.
I'm glad, because I wasn't having an
From: "Jeff Finn" <[EMAIL PROTECTED]>
Ok; I have generated a semi-self-contained Apache-test that will produce
this error.
I'm glad, because I wasn't having any luck producing a simple test
case that would work from IE, much less something more reproducible!
Hopefully now the mod_perl wizards can
Jeff Finn wrote:
Ok; I have generated a semi-self-contained Apache-test that will produce
this error.
This only happens on an SSL-enabled server
I was't able to get the alarm block working, but we can work around that
by starting the test, sleeping for a minute or so, and then in another
shell gett
PROTECTED]
Sent: Wednesday, August 04, 2004 11:45 PM
To: Jeff Finn
Cc: [EMAIL PROTECTED]
Subject: Re: ModPerl::Registry: Software caused connection abort
Jeff Finn wrote:
> I'm joining this thread a little late, but I just noticed I have a similar
> problem to this with Apache 2.0.49/50 and
Jeff Finn wrote:
I'm joining this thread a little late, but I just noticed I have a similar
problem to this with Apache 2.0.49/50 and mp1.99_14.
I have the server set up for responses to pass thru a filter:
PerlOutputFilterHandler Apache::FileProtector::output
When I use curl to access the server a
ersions of Apache 2.
i'm not sure how to go about working around this problem, does
anyone have some suggestions?
Thanks
Jeff
-Original Message-
From: Nick Phillips [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 5:21 PM
To: [EMAIL PROTECTED]
Subject: Re: ModPerl::Reg
On 03/08/2004, at 7:40 AM, Dan Wilga wrote:
At 12:02 PM -0700 8/2/04, Stas Bekman wrote:
Upon sending the response. The original error message happens in my
code when I try to "print" the HTTP header.
Yeah, that's what I thought. I suppose we could handle that
internally then. But I want to have
Dan Wilga wrote:
At 12:02 PM -0700 8/2/04, Stas Bekman wrote:
Upon sending the response. The original error message happens in my
code when I try to "print" the HTTP header.
Yeah, that's what I thought. I suppose we could handle that internally
then. But I want to have a failing test first. It s
At 12:02 PM -0700 8/2/04, Stas Bekman wrote:
Upon sending the response. The original error message happens in my
code when I try to "print" the HTTP header.
Yeah, that's what I thought. I suppose we could handle that
internally then. But I want to have a failing test first. It should
work with L
Dan Wilga wrote:
At 11:35 AM -0700 8/2/04, Stas Bekman wrote:
To start with I want to have a short test case that I can reproduce
the problem with. Too bad you had it happening only over SSL. We need
to check the Apache source to see, who else sends APR__ECONNABORTED
and hopefully have a simpler
At 11:35 AM -0700 8/2/04, Stas Bekman wrote:
To start with I want to have a short test case that I can reproduce
the problem with. Too bad you had it happening only over SSL. We
need to check the Apache source to see, who else sends
APR__ECONNABORTED and hopefully have a simpler test.
I'm not su
Dan Wilga wrote:
At 10:55 AM -0700 8/1/04, Stas Bekman wrote:
--- ModPerl-Registry/lib/ModPerl/RegistryCooker.pm27 Jun 2004
21:26:45 -1.50
+++ ModPerl-Registry/lib/ModPerl/RegistryCooker.pm1 Aug 2004
17:52:00 -
@@ -42,6 +42,7 @@
use File::Basename;
use Apache::Const -compi
At 10:55 AM -0700 8/1/04, Stas Bekman wrote:
--- ModPerl-Registry/lib/ModPerl/RegistryCooker.pm 27 Jun 2004
21:26:45 - 1.50
+++ ModPerl-Registry/lib/ModPerl/RegistryCooker.pm 1 Aug 2004
17:52:00 -
@@ -42,6 +42,7 @@
use File::Basename;
use Apache::Const -compile => qw(:common &OPT_EXEC
Dan Wilga wrote:
[...]
I have written to the Apache Developers' list, but the only suggestion I
got was that the initial "Connection reset by peer" error is to be
expected, but that mod_perl probably shouldn't be generating the pair of
"[error]" level log messages.
I don't entirely buy this, si
et by peer:
core_output_filter: writing data to the network
[Fri Jul 02 11:14:30 2004] [error] 5894: ModPerl::Registry: Software
caused connection abort at [path to script and line number].\n
[Fri Jul 02 11:14:30 2004] [error] 5894: ModPerl::Registry: Software
caused connection abort at [path to script and l
16 matches
Mail list logo
