Connected: An Internet Encyclopedia
RFC 1123 - 4.1.3.2 Idle Timeout

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1123
Up: 4. FILE TRANSFER
Up: 4.1 FILE TRANSFER PROTOCOL -- FTP
Up: 4.1.3 SPECIFIC ISSUES
Prev: 4.1.3.1 Non-standard Command Verbs
Next: 4.1.3.3 Concurrency of Data and Control

### 4.1.3.2 Idle Timeout

A Server-FTP process SHOULD have an idle timeout, which will terminate the process and close the control connection if the server is inactive (i.e., no command or data transfer in progress) for a long period of time. The idle timeout time SHOULD be configurable, and the default should be at least 5 minutes.

A client FTP process ("User-PI" in RFC-959) will need timeouts on responses only if it is invoked from a program.

DISCUSSION:

  Without a timeout, a Server-FTP process may be left pending indefinitely if the corresponding client crashes without closing the control connection.

Next: 4.1.3.3 Concurrency of Data and Control

Connected: An Internet Encyclopedia
RFC 1123 - 4.1.3.2 Idle Timeout