Differences
This shows you the differences between the selected revisions of the page.
| 2009-03-05 | 2009-04-15 | ||
| no auto proxy (martin) | no summary (202.58.180.57) (hidden) | ||
| Line 11: | Line 11: | ||
| First, select what type of proxy you want WinSCP to use for its network connections. The default setting is //None//. In this mode no proxy is used for the connection. | First, select what type of proxy you want WinSCP to use for its network connections. The default setting is //None//. In this mode no proxy is used for the connection. | ||
| - | 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 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. |
| - | + | ||
| - | 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. | + | |
| - | + | ||
| - | 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 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. | + | |
| ===== Username and Password ===== | ===== Username and Password ===== | ||