I'm experiencing difficulties using apache in the following environment. Is
there any good solution that would solve the security problems?
Server version: Apache/2.2.2
Server built: May 14 2006 18:14:53
PHP 5.1.4 (cli) (built: May 5 2006 19:14:55)
Virtual users are stored under /home/web/doma
> -Original Message-
> From: Chappidi, Sudhakar [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 29, 2006 8:33 AM
> To: users@httpd.apache.org
> Subject: [EMAIL PROTECTED] Apache 2.0 Unix restrict to single
> child process...
>
>
> Hello,
>
> Can anyone help me ?
>
> In Apache 2.0 How to
Hello,
Can anyone help me ?
In Apache 2.0 How to restrict to single child process in Unix.
Is there any configuration in httpd.conf for doing this.
I have tried giving the ServerLimit directive to one, but it doesn't
work.
INFO:
My Application is Iniitialized using the HTTP request and this
in
> -Original Message-
> From: Om [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 29, 2006 5:53 AM
> To: users@httpd.apache.org
> Cc: [EMAIL PROTECTED]
> Subject: Re: [EMAIL PROTECTED] separate logs for aliases
>
> Hi Shai,
> you can cross check once again in the apache2.2.2 manual.
> Check t
On 5/28/06, Sergey Tsalkov <[EMAIL PROTECTED]> wrote:
Anyone have any suggestions?
What you've described doesn't really look like a dangerous DOS-attack.
If clients just open connections and stay idle, there's a lot of good
workarounds:
1) lower timeout, and raise number of listening servers
2
Hi Shai,
you can cross check once again in the apache2.2.2 manual.
Check the Virtual hosts section.
I read that.
That configuration is working fine.
Can you please implement that and check once.
Thanks,
Om.
Shai wrote:
On 5/26/06, Brian Rectanus <[EMAIL PROTECTED]> wrote:
On 5/26/06, Shai <[EMA
On Sunday 28 May 2006 21:23, Sergey Tsalkov wrote:
> I'm using Apache 1.3.36.
*sigh*. Of course a server that's been obnsolete for more than
four years isn't up to date. Any 1.x server leaves you with every
connection tying up an entire process.
> mod_choke
Never heard of it.
> Nick, you ment
I'm using Apache 1.3.36. mod_choke is supposed to be able to limit the
number of connections per IP, but fails to do so for the reason
discussed earlier in this thread. mod_evasive, and anti-DoS tool, also
failed to stop the attack.
Nick, you mentioned that Apache 2.2 has built-in countermeasures
On Sunday 28 May 2006 19:23, Sergey Tsalkov wrote:
> This is very wrong. I can't figure out why Apache doesn't have any
> defense against such an obvious attack -- even the connection limiting
> modules can't help because they have no way of knowing that all the
> requests are coming from the same
On 5/28/06, Sergey Tsalkov <[EMAIL PROTECTED]> wrote:
This is very wrong. I can't figure out why Apache doesn't have any
defense against such an obvious attack -- even the connection limiting
modules can't help because they have no way of knowing that all the
requests are coming from the same IP
This has nothing to do with the server's ability to serve the content.
Heck, I can even reproduce the effect myself. If I simply run "telnet
localhost 80" from the server, a line like:
2-2 14313 0/3/52 R 0.024 3 0.0 0.010.09
? ? ..reading..
is
Error 408 means request timeout. Make sure your server isn't having an
issue serving the content.
If you can verify that it is an attack, then read the following; otherwise,
skip it.
While I will leave the Apache modding suggestions to the people here who are
sure to do so ... let me give you th
Hey guys.. My Apache was hit with a DoS attack, where the attacker was
opening connections to the server and not sending any data. It quickly
reached the MaxClients limit and prevented any further connections to
the server.
The Server Status was filled with lines like this:
7-2 40390/8/8
Hiyas,
I've been using apache 1.3 as a proxy server for a few years. A few days ago, I
finally updated my webservers, to run apache 2.0.58 (was using 1.3.33 before).
But, I found a really strange issue on this update. I had a VirtualHost
configuration which basically checked if a file was prese
14 matches
Mail list logo