docs.kde.org

Krishna Tateneni

Revision 3.00.00 (2002-02-11)

Table of Contents

Proxies
Introduction
Use
Authorization
Options
SOCKS

Proxies

Introduction

Proxies are programs running on a computer that acts a server on the network you are connected to (whether by modem or other means). These programs receive HTTP and FTP requests, retrieve the relevant files from the internet, and pass them on to the client computer that made the requests.

When you have configured a proxy, HTTP and/or FTP requests are re-routed through the computer that is acting as a proxy server. However, you can also select specific hosts which should be contacted directly, rather than through the proxy server. If you are on a local network, for example, access to local hosts probably doesn't need to go through a proxy server.

You should only need to configure a proxy server if your network administrator requires it (if you are a dial-up user, that would be your internet service provider or ISP). Otherwise, especially if you are feeling a bit confused about this proxy business, but everything seems to be fine with your internet connection, you don't need to change anything.

Please note that using proxy servers is optional, but has the benefit or advantage of giving you faster access to data on the internet.

If you are uncertain whether or not you need to use a proxy server to connect to the internet, please consult with your internet service provider's setup guide or your system administrator.

Use

Connect to the Internet directly

Select this option if you do not want to use a proxy server.

If you have decided to use a proxy, you have several methods to configure the settings for it.

Automatically detected script file

Select this option if you want the proxy setup configuration script file to be automatically detected and downloaded.

This option only differs from the next choice in that it does not require you to supply the location of the configuration script file. Instead, it will be automatically downloaded using “Web Access Protocol Discovery” (WAPD).

Note

If you have a problem using this setup, please consult the FAQ section at http://www.konqueror.org for more information.

Specified script file

Select this option if your proxy support is provided through a script file located at a specific address. You can then enter the address in the location text box, or use the folder icon to browse to it.

Preset environment variables

Some systems are setup with $HTTP_PROXY to allow graphical as well as non-graphical applications to share the same proxy configuration information.

If you know this applies to you, select this option and click on the Setup... button to provide the environment variable names used to set the address of the proxy server(s).

Manually specified settings

Select this option, and click on the Setup... to manually setup the location of the proxy servers to be used.

If you choose this option, another dialog will pop up.

The complete addressing information for the proxy includes both the internet address and a port number. You should enter these into the relevant text boxes. The arrow button copies the information from the HTTP line to the FTP line, in order to help save some typing.

If there are hosts which you can connect to without going through the proxy server, you can press Add to add the names of these hosts, separated by in the text box labeled No Proxy For:. For example, hosts that are on your local network can probably be contacted directly.

You can also choose Only use proxy for entries in this list.

Check this box to reverse the use of the exception list, i.e. the proxy servers will only be used when the requested URL matches one of the addresses listed here.

This features is useful if all you need is a proxy to access a few specific sites, for example, an internal intranet. If you have more complex requirements you might want to use a configuration script.

Authorization

Here you can choose between two types of authentication, if your proxy requires it. You can have Prompt as needed, the default, in which case Konqueror will only ask for a username or password if it needs to.

The other option is Use automatic login. Select this option if you have already set up a login entry for your proxy server in the $KDEDIR/share/config/kionetrc file.

Options

Use persistent connections to proxy

Use persistent connection to your proxy server. Keeps connection to proxy open, helps lower bandwidth/speed up connection. Enabling this option will require the proxy server's cooperation, if the proxy server does not support this, it will bring your internet to a stop.

SOCKS

Lauri Watts

SOCKS is a protocol to execute proxy requests for a client. SOCKS is capable of authentication and encryption of traffic, and is often found in corporate settings, as opposed to home users. For more information about SOCKS, see the NEC website

With this module you can enable most of the network aware KDE applications to transparently use SOCKS.

Setting up of a SOCKS client is outside the scope of this document, and the differences between the commonly used ones are very large. If you already have a working SOCKS implementation, allowing you to use commandline clients (for example, if lynx or ftp are already working) then you can simply check the Enable SOCKS support checkbox.

When this box is checked, several further options become available to you.

First, you should select which of the various SOCKS clients you have installed on your computer. KDE will attempt to find this out by itself, if you choose Auto detect. If you know the client you have, you could choose either NEC Socks or Dante. If you have a custom built SOCKS library to use, you can select Use custom library and then enter the path to it in the Path field.

If you want KDE to auto detect the SOCKS library in use, but you suspect it isn't looking in the right places or you have installed it in a non-standard location, then you can add further paths to be searched in the bottom of this panel. Use the Add and Remove to add or remove paths.

At any time while filling in this module, you can press the Test button, and KDE will report immediately with a message box to tell you if it could find and initialize SOCKS or not.

Changes made here will not affect any applications that are already open. You will need to close and restart them before they are able to connect via SOCKS.

 


docs.kde.org