It is more effective to use reverse proxy like nginx as a frontend. And use it to cut ddos requests.
You will need to setup it with a rule like "if the request does not contain auth cookie - send error.html ". May be more complex one because this can be hijacked with a fake cookie. Even more effective ways are to somehow identify bad requests and cut them with firewall or even router. On Wed, Oct 14, 2009 at 3:30 PM, Mats Henricson <m...@henricson.se> wrote: >>> Hi! >> >> Hi! > > Hi! > > You Tapestry guys are slow today. It took a whopping 8 minutes to > get an answer... ;-) > >>> So, what would you guys do? Is there a simpler solution? A filter? >> >> I would use a ResquestFilter or a Dispatcher checking some service (that >> would hold the underDDoS field) and redirecting to a given page when >> needed. > > Thanks a lot! I'll look at it! > > Mats > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
