Differences
This shows you the differences between the selected revisions of the page.
| 2017-12-21 | 2019-03-28 | ||
| 5.12 Bug 572 Amazon S3 protocol support. (martin) | typography (martin) | ||
| Line 30: | Line 30: | ||
| The option is not available with [[webdav|WebDAV]] and [[s3|S3]] protocols. | The option is not available with [[webdav|WebDAV]] and [[s3|S3]] protocols. | ||
| - | Note that keepalives are not always helpful. They help if you have a firewall which drops your connection after an idle period; but if the network between you and the server suffers from breaks in connectivity then keepalives can actually make things worse. If a session is idle, and connectivity is temporarily lost between the endpoints, but the connectivity is restored before either side tries to send anything, then there will be no problem - neither endpoint will notice that anything was wrong. However, if one side does send something during the break, it will repeatedly try to re-send, and eventually give up and abandon the connection. Then when connectivity is restored, the other side will find that the first side doesn't believe there is an open connection any more. Keepalives can make this sort of problem worse, because they increase the probability that WinSCP will attempt to send data during a break in connectivity. (Other types of periodic network activity can cause this behavior; in particular, [[ui_login_kex|SSH-2 re-keys]] can have this effect.) | + | Note that keepalives are not always helpful. They help if you have a firewall which drops your connection after an idle period; but if the network between you and the server suffers from breaks in connectivity then keepalives can actually make things worse. If a session is idle, and connectivity is temporarily lost between the endpoints, but the connectivity is restored before either side tries to send anything, then there will be no problem -- neither endpoint will notice that anything was wrong. However, if one side does send something during the break, it will repeatedly try to re-send, and eventually give up and abandon the connection. Then when connectivity is restored, the other side will find that the first side doesn't believe there is an open connection any more. Keepalives can make this sort of problem worse, because they increase the probability that WinSCP will attempt to send data during a break in connectivity. (Other types of periodic network activity can cause this behavior; in particular, [[ui_login_kex|SSH-2 re-keys]] can have this effect.) |
| Therefore, you might find that keepalives help connection loss, or you might find they make it worse, depending on what kind of network problems you have between you and the server.((&puttydoccite)) | Therefore, you might find that keepalives help connection loss, or you might find they make it worse, depending on what kind of network problems you have between you and the server.((&puttydoccite)) | ||