About client_header_timeout

Maxim Dounin mdounin at mdounin.ru
Mon Oct 19 11:02:15 MSD 2009


On Mon, Oct 19, 2009 at 02:01:24AM -0400, gunblad3 wrote:

> Hi guys,
> Would like to clarify on what client_header_timeout means exactly.
> http://wiki.nginx.org/NginxHttpCoreModule#client_header_timeout
> Using the default setting of 60 seconds, does it mean that the server times out the request:
> 1) if no additional request headers are received in 60 sec since the last one
> or
> 2) if the request (headers) should have completed within 60 sec of the start of the request?
> I believe it to be (1), but I'd like to make sure.

It's (2).

Note though that timeout is armed only when connection comes to 
nginx via accept().  This may not be at connection start from 
client's point of view if accept filters are used.

> Also, if it really is (1), is there a known bug where this timeout is not obeyed?

There is no known bugs related to client_header_timeout I'm aware of.

Maxim Dounin

More information about the nginx mailing list