# Nginx calls post body handler with no content?

**URL:** <https://www.ruby-forum.com/t/nginx-calls-post-body-handler-with-no-content/183564>\
**Category:** NGINX\
**Created:** [February 16, 2010, 5:15pm UTC](https://www.ruby-forum.com/t/nginx-calls-post-body-handler-with-no-content/183564 "2010-02-16T17:15:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tronman](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/e9c0ed/32.png) [@Tronman](https://www.ruby-forum.com/u/Tronman)\
**Post date:** [February 16, 2010, 5:15pm UTC](https://www.ruby-forum.com/t/nginx-calls-post-body-handler-with-no-content/183564/1 "2010-02-16T17:15:28Z")

</div>

Hey folks,

Is there something which might cause Nginx to call the post body handler  
(set with ngx\_http\_read\_client\_request\_body) before it actually reads  
the body? Maybe like a timeout or something?

I’ve been analyzing traffic with tcpdump, and most of the time, I see:

1. Headers (with content length)
2. Body (of content length size)
3. Response

but sometimes my handler gets a garbled buffer, and when I look in the  
tcpdump log I see:

1. Headers (with content length)
2. Response (an error since it doesn’t have the body)
3. Response Body
4. An error for the response body because it thinks it’s a request that  
doesn’t make sense.

I thought if maybe there was a timeout set somewhere, it returns without  
actually reading the request (if it was slow in coming) for some reason.  
But I can’t find a setting for anything like that anywhere.

If you have any advice, let me know! Thanks.

Posted at Nginx Forum:

> **[Nginx calls post body handler with no content?](https://forum.nginx.org/read.php?2,55098,55098#msg-55098)**
>
> Hey folks, Is there something which might cause Nginx to call the post body handler (set with ngx\_http\_read\_client\_request\_body) before it actually reads the body? Maybe like a timeout or something? I've been analyzing traffic with tcpdump, and most...