Re: [users@httpd] Which module is affected by the Range header issue?

2011-09-27 Thread Mark Montague
On September 27, 2011 12:50 , Steve Foster wrote: anyone? cheers.. On Wed, Aug 31, 2011 at 5:31 PM, Steve Foster mailto:stephenfoster1...@gmail.com>> wrote: i've also had a thought, I also implemented the following: LimitRequestLine 4000 Which is about half

Re: [users@httpd] Which module is affected by the Range header issue?

2011-09-27 Thread Steve Foster
anyone? cheers.. On Thu, Sep 8, 2011 at 6:14 PM, Steve Foster wrote: > All, > > did anyone have any thoughts or opinions on this? > > cheers > > Steve > > On Wed, Aug 31, 2011 at 5:31 PM, Steve Foster < > stephenfoster1...@gmail.com> wrote: > >> i've also had a thought, I also implemented the f

Re: [users@httpd] Which module is affected by the Range header issue?

2011-09-08 Thread Steve Foster
All, did anyone have any thoughts or opinions on this? cheers Steve On Wed, Aug 31, 2011 at 5:31 PM, Steve Foster wrote: > i've also had a thought, I also implemented the following: > > LimitRequestLine 4000 > > Which is about half of the default size i beleive, could this be limiting > the im

Re: [users@httpd] Which module is affected by the Range header issue?

2011-08-31 Thread Steve Foster
i've also had a thought, I also implemented the following: LimitRequestLine 4000 Which is about half of the default size i beleive, could this be limiting the impact on my servers and thus not making them vulnerable. Does anyone know what length of request the killapache script sends? cheers S

Re: [users@httpd] Which module is affected by the Range header issue?

2011-08-30 Thread Steve Foster
Correction , the static file gives a 206 status code... On Tue, Aug 30, 2011 at 4:14 PM, Steve Foster wrote: > Hi eric, > > yes i have tried it on a static file as well and no issues., obviously the > static file gives a 200 status code back in the logs, but i am still sending > the Range header

Re: [users@httpd] Which module is affected by the Range header issue?

2011-08-30 Thread Steve Foster
Hi eric, yes i have tried it on a static file as well and no issues., obviously the static file gives a 200 status code back in the logs, but i am still sending the Range header as per the kill script. Steve On Tue, Aug 30, 2011 at 3:42 PM, Eric Covener wrote: > > When you changes the resource

Re: [users@httpd] Which module is affected by the Range header issue?

2011-08-30 Thread Eric Covener
On Tue, Aug 30, 2011 at 10:31 AM, Steve Foster wrote: > > On Tue, Aug 30, 2011 at 3:18 PM, Eric Covener wrote: >> >> >> It's tuff baked into the core binary,  httpd.  Note that many dynamic >> responses can't be satisfied as range requests, so maybe your "/" is >> such a response. > > Hi eric, >

Re: [users@httpd] Which module is affected by the Range header issue?

2011-08-30 Thread Steve Foster
On Tue, Aug 30, 2011 at 3:18 PM, Eric Covener wrote: > > > It's tuff baked into the core binary, httpd. Note that many dynamic > responses can't be satisfied as range requests, so maybe your "/" is > such a response. > Hi eric, sorry i was referring to the compiled-in modules, e.g: Compiled i

Re: [users@httpd] Which module is affected by the Range header issue?

2011-08-30 Thread Eric Covener
On Tue, Aug 30, 2011 at 9:06 AM, Steve Foster wrote: > hi there, > > I have multiple versions of Apache, all built with minimal inclusions of > modules in the core binary , they don't exhibit the memory consumption issue > when attacked with the killapache script, they all run happily for hours >

[users@httpd] Which module is affected by the Range header issue?

2011-08-30 Thread Steve Foster
hi there, I have multiple versions of Apache, all built with minimal inclusions of modules in the core binary , they don't exhibit the memory consumption issue when attacked with the killapache script, they all run happily for hours with no resource issues. Does anyone know which particular modul