Differences
This shows you the differences between the selected revisions of the page.
| 2008-07-17 | 2008-07-17 | ||
| typography (martin) | unify socks version syntax (martin) | ||
| Line 11: | Line 11: | ||
| Selecting //HTTP// allows you to proxy your connections through a web server supporting the ''HTTP CONNECT'' command, as documented in RFC 2817. | Selecting //HTTP// allows you to proxy your connections through a web server supporting the ''HTTP CONNECT'' command, as documented in RFC 2817. | ||
| - | Selecting //SOCKS 4// or //SOCKS 5// 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. | ||
| Line 23: | Line 23: | ||
| Authentication is not fully supported for all forms of proxy: | Authentication is not fully supported for all forms of proxy: | ||
| - | * Username and password authentication is supported for HTTP proxies and SOCKS 5 proxies. | + | * Username and password authentication is supported for HTTP proxies and SOCKS5 proxies. |
| - | * With SOCKS 5, authentication is via CHAP if the proxy supports it, otherwise the password is sent to the proxy in plain text. | + | * With SOCKS5, authentication is via CHAP if the proxy supports it, otherwise the password is sent to the proxy in plain text. |
| * With HTTP proxying, the only currently supported authentication method is "basic", where the password is sent to the proxy in plain text. | * With HTTP proxying, the only currently supported authentication method is "basic", where the password is sent to the proxy in plain text. | ||
| - | * SOCKS 4 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. | ||
| Line 51: | Line 51: | ||
| If you set this option to //Auto// (the default), WinSCP will do something it considers appropriate for each type of proxy. Telnet, HTTP and SOCKS5 proxies will have host names passed straight to them; SOCKS4 proxies will not. | If you set this option to //Auto// (the default), WinSCP will do something it considers appropriate for each type of proxy. Telnet, HTTP and SOCKS5 proxies will have host names passed straight to them; SOCKS4 proxies will not. | ||
| - | The original SOCKS 4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS 4A) which does support it, but not all SOCKS 4 servers provide this extension. If you enable proxy DNS and your SOCKS 4 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. |
| ===== 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)) | ||