Differences
This shows you the differences between the selected revisions of the page.
| 2017-02-02 | 2017-12-21 | ||
| connection explicit anchor (martin) | 5.12 Bug 572 Amazon S3 protocol support. (martin) | ||
| Line 14: | Line 14: | ||
| Use //Passive mode// to toggle between //passive// and //active// [[ftp_modes|FTP connection mode]]. //Passive// mode is selected by default. The option is supported only with FTP protocol. | Use //Passive mode// to toggle between //passive// and //active// [[ftp_modes|FTP connection mode]]. //Passive// mode is selected by default. The option is supported only with FTP protocol. | ||
| - | The //Optimize connection buffer size// enables optimization of socket buffer size. It greatly improves transfer speed. Disable it only when experiencing problems. The option is not available with [[webdav|WebDAV protocol]]. | + | The //Optimize connection buffer size// enables optimization of socket buffer size. It greatly improves transfer speed. Disable it only when experiencing problems. The option is not available with [[webdav|WebDAV]] and [[s3|S3]] protocols. |
| ===== [[timeout]] Timeouts ===== | ===== [[timeout]] Timeouts ===== | ||
| Line 28: | Line 28: | ||
| As an alternative WinSCP can send dummy commands of the transfer protocol instead. For %%SFTP%% it is implemented as canonization of path ''/''. For %%SCP%% it is implemented as ''echo'' command.((With %%SCP%% this keepalive method does not work while WinSCP waits for user prompt in the middle of file transfer.)) For FTP it is the only option and is implemented as randomly selected %%FTP%% protocol command with no effect. | As an alternative WinSCP can send dummy commands of the transfer protocol instead. For %%SFTP%% it is implemented as canonization of path ''/''. For %%SCP%% it is implemented as ''echo'' command.((With %%SCP%% this keepalive method does not work while WinSCP waits for user prompt in the middle of file transfer.)) For FTP it is the only option and is implemented as randomly selected %%FTP%% protocol command with no effect. | ||
| - | The option is not available with [[webdav|WebDAV protocol]]. | + | 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.) | ||
| Line 40: | Line 40: | ||
| explicitly set this to //IPv4// or //%%IPv6%%//. ((&puttydoccite)) | explicitly set this to //IPv4// or //%%IPv6%%//. ((&puttydoccite)) | ||
| - | The option is not available with [[webdav|WebDAV protocol]]. | + | The option is not available with [[webdav|WebDAV]] and [[s3|S3]] protocols. |
| ===== Further Reading ===== | ===== Further Reading ===== | ||
| Read more about [[ui_login|Login dialog]] and [[ui_login_advanced|Advanced Site Settings dialog]]. | Read more about [[ui_login|Login dialog]] and [[ui_login_advanced|Advanced Site Settings dialog]]. | ||