X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/6ee9b735013c0e636b027b77e9f6ba57a96e142f..b7a189f38294c745ae4ea6efb55891c8196e275b:/doc/config.but diff --git a/doc/config.but b/doc/config.but index bbe8495f..909d60fb 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.45 2002/12/18 11:39:25 simon Exp $ +\versionid $Id: config.but,v 1.47 2002/12/18 16:23:10 simon Exp $ \C{config} Configuring PuTTY @@ -1439,6 +1439,49 @@ from proxying. This excludes both of the above ranges at once. +Connections to the local host (the host name \c{localhost}, and any +loopback IP address) are never proxied, even if the proxy exclude +list does not explicitly contain them. It is very unlikely that this +behaviour would ever cause problems, but if it does you can change +it by enabling \q{Consider proxying local host connections}. + +Note that if you are doing DNS at the proxy (see +\k{config-proxy-dns}), you should make sure that your proxy +exclusion settings do not depend on knowing the IP address of a +host. If the name is passed on to the proxy without PuTTY looking it +up, it will never know the IP address and cannot check it against +your list. + +\S{config-proxy-dns} Name resolution when using a proxy + +\cfg{winhelp-topic}{proxy.dns} + +If you are using a proxy to access a private network, it can make a +difference whether DNS name resolution is performed by PuTTY itself +(on the client machine) or performed by the proxy. + +The \q{Do DNS name lookup at proxy end} configuration option allows +you to control this. If you set it to \q{No}, PuTTY will always do +its own DNS, and will always pass an IP address to the proxy. If you +set it to \q{Yes}, PuTTY will always pass host names straight to the +proxy without trying to look them up first. + +If you set this option to \q{Auto} (the default), PuTTY will do +something it considers appropriate for each type of proxy. Telnet +and HTTP proxies will have host names passed straight to them; SOCKS +proxies will not. + +Note that if you are doing DNS at the proxy, you should make sure +that your proxy exclusion settings (see \k{config-proxy-exclude}) do +not depend on knowing the IP address of a host. If the name is +passed on to the proxy without PuTTY looking it up, it will never +know the IP address and cannot check it against your list. + +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. + \S{config-proxy-auth} Username and password \cfg{winhelp-topic}{proxy.auth}