Wiki updated with reset_timedout_connection

Hello,

I’ve updated the Wiki with a directive that was missing from the
english version:
http://wiki.nginx.org/HttpCoreModule#reset_timedout_connection

I’ve used the translation provided by Google of the original
documentation at:
http://sysoev.ru/nginx/docs/http/ngx_http_core_module.html#reset_timedout_connection

The translation leaves quite a lot to be desired :frowning:

Can someone knowledgeable in Russian and/or Nginx internals verify
this for correctness?

Thank you,
— appa

This directive enables or disables resetting the connection upon
timeout. When resetting the connection, before the socket is closed,
the SO_LINGER option is set to the socket with timeout value of 0, which
forces RST packet to be sent to client upon closing the socket, while
all memory associated with the socket is freed. This allows to avoid
the situation when the already closed socket is in the FIN_WAIT1 state
with the loaded buffers.

The keepalive connections, after timeout, are closed in the usual way.

Posted at Nginx Forum:

On 15 Jul 2011 18h23 WEST, [email protected] wrote:

Hello Andrejs,

This directive enables or disables resetting the connection upon
timeout. When resetting the connection, before the socket is
closed, the SO_LINGER option is set to the socket with timeout value
of 0, which forces RST packet to be sent to client upon closing the
socket, while all memory associated with the socket is freed. This
allows to avoid the situation when the already closed socket is in
the FIN_WAIT1 state with the loaded buffers.

The keepalive connections, after timeout, are closed in the usual
way.

Thank you for your translation. Google translate really sucks :frowning:
I ended up with this:

syntax: reset_timedout_connection [on|off]

default: reset_timedout_connection off

context: http, server, location

This directive enables or disables resetting the connection on
timeout. When resetting the connection, before the socket is closed,
the socket SO_LINGER option is set with a 0 timeout, which forces a
RST packet to be sent to the client upon closing the socket, thus
freeing all memory associated with it. This prevents that a socket
in the FIN_WAIT1 state keep the buffers associated with it lying
around.

Note that sockets with keepalive connections, after the defined
timeout, are closed in the usual way.

I hope it’s clearer and more faithful to the original docs.
— appa

António P. P. Almeida Wrote:

On 15 Jul 2011 18h23 WEST, [email protected]
wrote:

This directive enables or disables resetting the
connection on
timeout. When resetting the connection, before
the socket is closed,
the socket SO_LINGER option is set with a 0
timeout, which forces a
RST packet to be sent to the client upon closing

“the” RST packet, I think, since we mention what kind it is.

the socket, thus
freeing all memory associated with it. This
prevents that a socket
in the FIN_WAIT1 state keep the buffers
associated with it lying
around.

This prevents the socket in the FIN_WAIT1 state, along with the buffers
associated with it from lying around.

(“the socket” – since we’re talking about the specific socket)

Kudos on working with the English manual!

Andrejs

Posted at Nginx Forum:

On 15 Jul 2011 19h21 WEST, [email protected] wrote:

“the” RST packet, I think, since we mention what kind it is.

This prevents the socket in the FIN_WAIT1 state, along with the
buffers associated with it from lying around.

(“the socket” – since we’re talking about the specific socket)

Kudos on working with the English manual!

Done. I’ve learned a lot by reading and working on it.

Andrejs

Thank you,
António