On Mon, Sep 22, 2008 at 08:16:01AM +0200, Stefan Fritsch wrote:
> On Monday 22 September 2008, Felipe Figueiredo wrote:
> > > Try modsecurity, it should block invalid URI
> >
> > Speaking of which, shouldn't it be re-included in Debian now that
> > the licensing issue[1] is supposed to be over[2]?
On Monday 22 September 2008, Felipe Figueiredo wrote:
> > Try modsecurity, it should block invalid URI
>
> Speaking of which, shouldn't it be re-included in Debian now that
> the licensing issue[1] is supposed to be over[2]?
There is already an ITP bug, but I don't know the current status.
http:/
On Mon, 2008-09-22 at 09:15 +1000, Stephen Vaughan wrote:
> Try modsecurity, it should block invalid URI
>
Speaking of which, shouldn't it be re-included in Debian now that the
licensing issue[1] is supposed to be over[2]?
1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352344
2. http://blo
It sounds liek your app, or a combination of the modules you're using is
more likely what's running Apache out of memory. mod_security could be
used to check for requests that contain just a numeric path to GET, but I'd
investigate why your app/configuration is causing an OOM error. Could it
Try modsecurity, it should block invalid URI
On Mon, Sep 22, 2008 at 8:08 AM, NeMiX <[EMAIL PROTECTED]> wrote:
> Hi there,
>
>
>
> since last week we´ve got a little problem with our Webserverfarm.
>
> We get some strange Request from some Dial-Up Accounts from Europe
> (T-Online; Telefonica; Or
Hi there,
since last week we´ve got a little problem with our Webserverfarm.
We get some strange Request from some Dial-Up Accounts from Europe
(T-Online; Telefonica; Orange...):
Sep 21 22:47:35 logger: [Sun Sep 21 22:47:35 2008] [error] [client
87.183.65.xx] Invalid URI in request GET 347
6 matches
Mail list logo