William A. Rowe, Jr. wrote:
Fascinating reading (see the bottom two tables of these pages:
http://www.securityspace.com/s_survey/data/man.200501/srvch.html?server=Apacherevision=Apache%2F1.3.33
http://www.securityspace.com/s_survey/data/man.200501/srvch.html?server=Apacherevision=Apache%2F2.0.52
Hi Arkadi,
We've run into a similar problem. I didn't quite understand the second
solution that you suggested. How would closing the read side of the pipe
in the httpd child processes help in solving this problem ?
Thanks,
Kiran
Arkadi Shishlov wrote:
On Tue, Mar 08, 2005 at 01:22:46PM -0500,
At 05:48 AM 3/14/2005, Ben Laurie wrote:
William A. Rowe, Jr. wrote:
Fascinating reading (see the bottom two tables of these pages:
http://www.securityspace.com/s_survey/data/man.200501/srvch.html?server=Apacherevision=Apache%2F1.3.33
William A. Rowe, Jr. [EMAIL PROTECTED] writes:
[...]
In that particular window (of a month) more folks took
Apache 2.0.x servers down in favor of 1.3.x servers,
than those who upgraded to 2.0.x from 1.3.x.
That may be explainable by someone familiar with the
hosteurope.de anomaly in the
*long but interesting, I hope*
I had the displeasure of coping with a large DDOS attack this weekend
and tested out how apache 2.1.3-beta did. It didn't do very well at all.
I realize this list is for discussion of changes to the source code and
related issues but I'm hoping this is still
A customer reported a problem where their back end app would hang until a read
timed out. The main request was a POST which did have a request body which was
read normally. The POST response contained an ssi tag that caused a subrequest
to be created. The subrequest was forwarded to an app
I think it is slightly deceptive to say 2.1.3-beta doesn't handle a DDoS
attack very well -- 1.3.x or 2.0.x would not do any better.
[EMAIL PROTECTED] wrote:
*long but interesting, I hope*
Few comments:
1) There was a memory leak in the core_input_filter. It has been fixed
in /trunk/, but
Greg Ames [EMAIL PROTECTED] writes:
[...]
As it turns out, we clone all of the main request's input headers when
we create the subrequest, including C-L. Whacking the subrequest's
C-L header fixes the hang. Since the main request's body could also
have be chunked, we should probably remove
Hi All,
Apache is already passing client IP addr to the backend server via a
mechanism of headers:
X-Forwarded-For
X-Forwarded-Host
X-Forwarded-Server
The difficulty is that very often the backend server is an Apache
server from a vendor, and any changes to the server will void support.
There
On Tue, 15 Mar 2005 13:25:52 +1100 (EST), Jie Gao
[EMAIL PROTECTED] said:
Hi All,
Apache is already passing client IP addr to the backend server via a
mechanism of headers:
X-Forwarded-For
X-Forwarded-Host
X-Forwarded-Server
The difficulty is that very often the backend server is an
On Mon, 14 Mar 2005, Joshua Slive wrote:
Date: Mon, 14 Mar 2005 22:20:39 -0500
From: Joshua Slive [EMAIL PROTECTED]
Reply-To: dev@httpd.apache.org
To: dev@httpd.apache.org
Subject: Re: feature proposal
On Tue, 15 Mar 2005 13:25:52 +1100 (EST), Jie Gao
[EMAIL PROTECTED] said:
Hi All,
I would like to roll the 2.1.4 alpha right after APR 1.1.1 is released.
I plan on rolling APR tonight or Tuesday morning. If there arent any
problems, I am hoping to create 2.1.4 on Thursday. Any big outstanding
issues?
Thanks,
-Paul
On Mon, 14 Mar 2005 19:35:52 +0100 (GMT-1), Damir Dezeljin
[EMAIL PROTECTED] wrote:
I'm wondering if APR OS400 port sources are publicaly available? Does
anyone know anything about this? What about apache sources?
I have no idea of the OS/400 patches and/or full sources they use are
publically
13 matches
Mail list logo
