Differences
This shows you the differences between the selected revisions of the page.
| 2009-03-05 | 2009-09-03 | ||
| no auto proxy (martin) | bug 27 (martin) | ||
| Line 15: | Line 15: | ||
| Selecting //SOCKS4// or //SOCKS5// allows you to proxy your connections through a SOCKS server. | Selecting //SOCKS4// or //SOCKS5// allows you to proxy your connections through a SOCKS server. | ||
| - | Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine and enter a command such as ''connect myhost.com 22'' to connect through to an external host. Selecting //Telnet// allows you to tell WinSCP to use this type of proxy. | + | Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine and enter a command such as ''connect myhost.com 22'' to connect through to an external host. Selecting //Telnet// allows you to tell WinSCP to use this type of proxy. This type of proxy is not supported for [[protocols#ftp|FTP protocol]]. |
| - | Selecting //Local// allows you to specify an arbitrary command on the local machine to act as a proxy. When the session is started, instead of creating a TCP connection, WinSCP runs the specified command, and uses its standard input and output streams. | + | Selecting //Local// allows you to specify an arbitrary command on the local machine to act as a proxy. When the session is started, instead of creating a TCP connection, WinSCP runs the specified command, and uses its standard input and output streams. This type of proxy is not supported for FTP protocol. |
| - | This could be used, for instance, to talk to some kind of network proxy that WinSCP does not natively support; or you could tunnel a connection over something other than TCP/IP entirely. | + | This could be used, for instance, to talk to some kind of network proxy that WinSCP does not natively support; or you could tunnel a connection over something other than TCP/IP entirely. |
| + | |||
| + | For [[protocols#ftp|FTP protocol]] set of methods to connect over FTP proxies is supported. The methods differ by sequence of commands needed to instruct the proxy to connect to target host. The most typical method is //USER %user@%host//. | ||
| ===== Username and Password ===== | ===== Username and Password ===== | ||
| Line 30: | Line 32: | ||
| * SOCKS4 can use the //Username// field, but does not support passwords. | * SOCKS4 can use the //Username// field, but does not support passwords. | ||
| * You can specify a way to include a username and password in the //Telnet/Local// proxy command. | * You can specify a way to include a username and password in the //Telnet/Local// proxy command. | ||
| + | * Most FTP proxy methods do require authentication. | ||
| ===== Telnet/Local Proxy Command ===== | ===== Telnet/Local Proxy Command ===== | ||
| Line 54: | Line 57: | ||
| The original SOCKS4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS4A) which does support it, but not all SOCKS4 servers provide this extension. If you enable proxy DNS and your SOCKS4 server cannot deal with it, this might be why. | The original SOCKS4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS4A) which does support it, but not all SOCKS4 servers provide this extension. If you enable proxy DNS and your SOCKS4 server cannot deal with it, this might be why. | ||
| + | |||
| + | These options are not supported for [[protocols#ftp|FTP protocol]]. | ||
| ===== Proxying Local Host Connections ===== | ===== Proxying Local Host Connections ===== | ||
| Connections to the local host (the host name ''localhost'', and any loopback IP address) are not proxied by default. It is very unlikely that this behavior would ever cause problems, but if it does you can change it by enabling //Consider proxying local host connections//. ((&puttydoccite)) | Connections to the local host (the host name ''localhost'', and any loopback IP address) are not proxied by default. It is very unlikely that this behavior would ever cause problems, but if it does you can change it by enabling //Consider proxying local host connections//. ((&puttydoccite)) | ||
| + | |||
| + | This option is not supported for [[protocols#ftp|FTP protocol]]. | ||