Re: Very long URL with malice intended

2004-03-31 Thread GROG! (Jeff Howie)
On Sat, 27 Mar 2004 15:50:53 -0600, Jack L. Stone wrote: At 08:28 PM 3.27.2004 +0100, Cordula's Web wrote: Within the past couple of weeks, the Apache logs have shown a new type of intrusion -- a very, very long URL request... My question is what syntax can I add, if any, to my httpd.conf to

RE: Very long URL with malice intended

2004-03-31 Thread Toni Heinonen
On Sat, 27 Mar 2004 15:50:53 -0600, Jack L. Stone wrote: At 08:28 PM 3.27.2004 +0100, Cordula's Web wrote: Within the past couple of weeks, the Apache logs have shown a new type of intrusion -- a very, very long URL request... My question is what syntax can I add, if any, to my httpd.conf

RE: Very long URL with malice intended

2004-03-31 Thread Nick
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of GROG! (Jeff Howie) Sent: Wednesday, March 31, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Re: Very long URL with malice intended On Sat, 27 Mar 2004 15:50:53 -0600, Jack L. Stone

Re: Very long URL with malice intended

2004-03-31 Thread GROG! (Jeff Howie)
On Wed, Mar 31, 2004 at 06:32:53PM +0300, Toni Heinonen wrote: On Sat, 27 Mar 2004 15:50:53 -0600, Jack L. Stone wrote: At 08:28 PM 3.27.2004 +0100, Cordula's Web wrote: Within the past couple of weeks, the Apache logs have shown a new type of intrusion -- a very, very long URL request... My

Re: Very long URL with malice intended

2004-03-27 Thread Cordula's Web
Within the past couple of weeks, the Apache logs have shown a new type of intrusion -- a very, very long URL request -- that finally receives a error 414. I don't know the purpose of this one, but doesn't appear well-intended. It comes late at night and from different IPs. One request even

Re: Very long URL with malice intended

2004-03-27 Thread Jack L. Stone
At 08:28 PM 3.27.2004 +0100, Cordula's Web wrote: Within the past couple of weeks, the Apache logs have shown a new type of intrusion -- a very, very long URL request -- that finally receives a error 414. I don't know the purpose of this one, but doesn't appear well-intended. It comes late at