The Options Connection screen allows you to configure the ZAP connection options:
This makes is easier to test slow applications.
The user agent that ZAP should use when creating HTTP messages (for example, spider messages or CONNECT requests to outgoing proxy).
Controls whether the ZAP’s managed cookies (Enable (Global) HTTP State) should be set on a single “Cookie” request header or multiple “Cookie” request headers, when sending an HTTP request to the server.
This allows session details stored in cookies to be tracked.
This option must be selected to enable the “Use current tracking session” checkbox in the Manual Request Editor dialogs.
Session tracking ensures that any requests are sent with the latest session details.
For example you may record a session when logged in as one user and then logout and login as another user.
If you resend a request from the first session without session tracking then it will use the cookies from the first session.
If you resend the same request with session tracking then it will use the cookies from the second session.
Defines for how long the successful DNS queries should be cached:
Note: Changes are applied after a restart.
The option can also be set using the -config command line argument with the key connection.dnsTtlSuccessfulQueries.
Allows to choose the SSL/TLS versions enabled for outgoing connections (for example, to servers). At least one version must be enabled, versions unsupported by the JRE will be unselected and disabled.
The option SSLv2Hello must be selected in conjunction with at least one SSL/TLS version.
This section allows you to connect to another proxy for outgoing connections.
This is often required in a corporate environment.
This section allows you to configure the outgoing proxy authentication.
This section allows you to configure an outgoing SOCKS proxy, by default the SOCKS proxy configuration applies to all connections made by ZAP.
The SOCKS proxy system properties (e.g. socksProxyHost, socksProxyPort) take precedence over the persisted configurations
for compatibility with older ZAP versions. ZAP will use and display the values of the system’s properties when defined at startup, the configurations
can still be changed in this panel.
Note: Loopback addresses (e.g. localhost, 127.0.01, ::1) are not proxied through the SOCKS proxy, the connections will be done directly.
If ZAP should use the configured SOCKS proxy.
Default: unselected, unless the SOCKS proxy system properties are defined, in which case it is selected.
The host name or address of the SOCKS proxy.
Default: localhost.
The port of the SOCKS proxy.
Default: 1080.
The version of the SOCKS proxy.
Default: 5.
If ZAP should let the SOCKS proxy resolve the host names. Requires a version 5 SOCKS proxy.
This might lead to connection failures if the SOCKS proxy is not able to resolve the host name (e.g. use of names that are defined in a hosts file).
Default: selected.
The following fields allow to configure the authentication credentials for the SOCKS proxy.
The user name.
Default: none.
The password.
Default: none.
Note: Stored in clear text in the configuration file.
| UI Overview | for an overview of the user interface | |
| Options dialogs | for details of the other Options dialog screens | |
| Command Line | for details of the Command Line |