From: Yohanes Santoso Date: 2005-10-24T21:26:51+09:00 Subject: Re: I want my MOM "Zed A. Shaw" writes: > On Mon, 24 Oct 2005 13:50:08 +0900 > Yohanes Santoso wrote: > >> "Zed A. Shaw" writes: >> >> 5) Require that the header MUST have the >> > content-length settings. This is again to make sure that requests >> > which are too large are always booted. Making this optional just >> > leaves open an attack where you again slam the server with never >> > ending data until it dies. This also makes it very clear how the >> > content is always sent and leaves nothing open for debate. >> >> To add to what Zed's said: >> >> Servers can always prevent trickle attack by specifying a >> timeout. Without any timeout from server, a client would always be >> able to tie up unnecessary resources (IP port, for example). >> >> Most HTTP/1.1 servers close idle persistent connection after 2 minutes >> of inactivity. >> >> Again, server implementations should employ some sort of timeout >> mechanism. That's just the right thing to do. >> >> YS. >> > > That misses the point of the trickle attack. I just trickle enough to > never be idle but slowly eat up memory. > Since the server can't boot me as I might be legit, The server must have the ability to boot you if you pass a certain timeout. And there are many kinds of timeout policies, e.g.: a minimum traffic rate of x byte/y time (i've never seen this one), a maximum of x time for a request/response process to be done (i see this a lot in financial-related protocols), a maximum of x time for idle connection (HTTP/1.1 uses this particular one). YS.