|
Option |
Description |
Default |
|---|---|---|
| Active Provider | Specifies the settings profile to be used when opening connections. Choosing the Direct provider causes all the connections to be opened without the use of a proxy server. Selecting Manual causes settings defined in Eclipse to be used. On some platforms there is also a Native provider available, selecting this one causes settings that were discovered in the OS to be used. | Native (if present) Manual (otherwise) |
| Proxy entries | The table displays entries that are available for all providers. Checkboxes in the first column of the table indicate entries to be used for the currently selected provider. | |
| Proxy bypass | Use this table to specify, either by name or pattern, which hosts should not use any proxy. A direct connection will always be used for matching hosts. Checkboxes in the first column of the table indicate entries to be used for the currently selected provider. |
Proxy entries
When using Manual proxy provider there are three predefined schemas to set settings for: HTTP, HTTPS and SOCKS [1]. Configuration for each schema is displayed in the Proxy entries table. To edit settings for a particular schema double-click the entry or select the entry and click Edit... button. If Port field is left blank default port number will be used. Following table lists default port numbers for each of the predefined schemas.
|
Schema |
Default Port |
|---|---|
| HTTP | 80 |
| SSL | 443 |
| SOCKS | 1080 |
1. The SOCKS proxy support in Java 1.4 had certain limitations. Due to these limitations, the setting of the SOCKS system properties is not performed when a 1.4 VM is used. The SOCKS proxy may still be used by some tooling when running on a 1.4 VM (e.g. CVS). However, users should use a 1.5 (or 5.0) VM if they require full SOCKS proxy support.