BugTraq
a cheesy Apache / IIS DoS vuln (+a question) Jan 03 2007 11:27PM Michal Zalewski (lcamtuf dione ids pl) (4 replies) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 05 2007 08:45AM bugtraq (bugtraq securityfocus lists bitrouters com) (1 replies) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 09 2007 06:15AM William A. Rowe, Jr. (wrowe rowe-clan net) (1 replies) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 10 2007 10:04AM bugtraq (bugtraq securityfocus lists bitrouters com) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 04 2007 12:36PM Siim Põder (windo p6drad-teel net) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 04 2007 11:45AM Pieter de Boer (pieter thedarkside nl) (1 replies) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 04 2007 06:47PM Rob Sherwood (capveg cs umd edu) Re: a cheesy Apache / IIS DoS vuln (+a question) Jan 04 2007 05:35AM William A. Rowe, Jr. (wrowe rowe-clan net) (2 replies) |
Privacy Statement |
> Seriously, HTTP pipelining can accomplish EXACTLY the same thing with minimal
> pain.
No, it can't. Client-side pipelining using simultaneous sessions with
keep-alives is usually severely restricted on server-side (exactly for the
reason they can be abused to DoS the server), and the overhead is much
higher (you need to send hundreds of bytes to request a copy of a static
page).
Here, requesting an extra copy costs you 3 bytes, and that is in my
opinion notable - because you can do it thousands of times in a single
short request.
> If you have an issue with this behavior, of HTTP, then you have an issue
> with the behavior under FTP or a host of other protocols.
Not really; see above. These are typically well known, preventable by
configuring server-side limits, and require a much higher overhead.
/mz
[ reply ]