# Query: HTTP POST DoS

**URL:** <https://www.ruby-forum.com/t/query-http-post-dos/199490>\
**Category:** NGINX\
**Created:** [November 22, 2010, 8:55pm UTC](https://www.ruby-forum.com/t/query-http-post-dos/199490 "2010-11-22T20:55:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![okkezSS](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/85f322/32.png) [@okkezSS](https://www.ruby-forum.com/u/okkezSS)\
**Post date:** [November 22, 2010, 8:55pm UTC](https://www.ruby-forum.com/t/query-http-post-dos/199490/1 "2010-11-22T20:55:56Z")

</div>

Hi,

How does nginx react to an attack of this kind:

> **[HTTP Post Denial Of Service: more dangerous than initially thought](https://www.acunetix.com/blog/articles/http-post-denial-service/)**
>
> What's special about this denial of service attack is that it's very hard to fix because it relies on a generic problem in the way HTTP protocol works

-Naresh V.

---

<div class="post-metadata">

**Author:** ![Naresh\_V](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/c4cdca/32.png) [@Naresh\_V](https://www.ruby-forum.com/u/Naresh_V)\
**Post date:** [November 28, 2010, 1:37pm UTC](https://www.ruby-forum.com/t/query-http-post-dos/199490/2 "2010-11-28T13:37:04Z")

</div>

It should handle ok since its event based (not thread based), as long as  
the  
number of connections limit is high enough should be no worse than a  
keep-alive connection.