...
Recording can also be done of web surfing sessions of client programs.
Support for Technical Client Programs and Web Services (SOAP/XML, JSON and Google Protobuf over HTTP/S)
A Web browser is only required in order to use the Web Admin GUI. This means that you can also record web surfing sessions of (non Web browser based) technical client programs which exchange ASCII, SOAP/XML, JSON or Google Protobuf data with the Web server by using the HTTP/S protocol. Please note that you have to configure the proxy settings of the technical client program to record web surfing sessions. In case if the technical Web client uses encrypted HTTPS connections, you have also to import your CA Root Certificate into the technical Web client (see Installation Guide).
Furthermore it's also supported to create manually a text file by using any text editor which contains definitions of SOAP and/or XML requests. Such a file can then be converted to a Web surfing session by using the import functionality of the Session Cutter .
Proxy Recorder Settings and GUI Settings (Personal Settings Menu)
The “Personal Settings” menu allows you to configure non form-based authentication methods (NTLM, PKCS# 11, PKCS# 12 and DER/PEM based client certificates) and some SSL options for the proxy recorder which may be necessary in order to successfully record a Web surfing session. Furthermore, cascading the proxy recorder with another (outbound) proxy server of your company is also supported.
...
Additionally, also Alert Notifications can be configured which are send during the execution of a job as Emails or as SMS messages
Connect to Next Proxy (Proxy Recorder)
Checkbox in Title: if checked, ZebraTester cascades the proxy recorder with another, "next", outbound proxy server of your company.
Note: To execute a load test through a proxy server, you must also enable the option Load Test over HTTP(S) Proxy in the Generate HTTP(S) Load Test Program menu .
Input Fields
Next Proxy HTTP Host | (DNS) hostname or TCP/IP address of the next proxy server (for unencrypted connections). | |
Next Proxy HTTP Port | HTTP TCP/IP port number of the next proxy server (for unencrypted connections). | |
Next Proxy HTTP Cache disabled | if checked, request the next proxy server to disable its internal cache. | |
Next Proxy HTTPS Host | (DNS) hostname or TCP/IP address of the next proxy server (for encrypted connections). | |
Next Proxy HTTPS Port | HTTPS (secure) TCP/IP port number of the next proxy server (for encrypted connections). | |
Next Proxy Auth Username | basic authentication username, used for proxy authentication on the next proxy server. | |
Next Proxy Auth Password | basic authentication password, used for proxy authentication on the next proxy server. | |
No Next Proxy for Host/Domain | allows you to set a list of hosts, or domain names, for which the proxy settings must not be applied. The entries must be separated by commas or semicolons. |
HTTPS Settings (Proxy Recorder)
Allows you to adjust the HTTPS settings of the proxy recorder (used when recording encrypted network connections).
Input Fields
SSL Version | Allows you to select the SSL protocol version. | |
HTTPS Response Timeout | Response timeout per HTTPS URL call. If this timeout expires, the corresponding HTTPS URL call will be aborted. | |
SSL Session Cache enabled | If checked, enables the SSL session cache (keeping the same SSL session ID over multiple Web pages). | |
SSL Session Cache Timeout | The lifetime of the SSL sessions within the session cache. | |
Allow Legacy Renegotiation | If checked, SSL legacy renegotiation without using the Renegotiation Indication Extension (RFC 5746) is supported. | |
Support Elliptic Curves | If checked, also rarely used encryption algorithms like ECC are enabled. This means that all available encryption algorithms are enabled (inclusive very weak and very strong algorithms). | |
SNI enabled | If checked, Server Name Indication (SNI) information about the target host name is sent to the Web server(s) during the SSL handshake (RFC 3546). | |
SNI critical | If checked and SNI is enabled, SSL handshakes are aborted if the target Web server(s) doesn't support Server Name Indication (SNI). The corresponding HTTP requests will fail in such a case and no data are recorded. | |
Enhanced Compatibility Mode | If checked, enables workarounds to support poorly-implemented SSL server libraries. | |
Debug Handshakes | If checked, debug information about SSL/TLS Handshakes are written to stdout or to the ZebraTester Console. |
HTTPS Client Certificate Authentication - PKCS# 12 Files (Proxy Recorder)
Allows you to load X509 SSL/TLS client certificates, in PKCS# 12 file-format, into the proxy recorder. Because the proxy recorder operates as a man in the middle between the Web browser and the Web server, the client certificate must be loaded and activated before a Web surfing session requiring such a certificate can be recorded.
...
The PKCS# 12 file must first be loaded by using the Personal Settings menu. Also ensure that the certificate is active by clicking inside the red bar on the certificate. The red bar will change to a green check mark when the certificate is properly active.
Note: To execute a load test which uses client certificates, you must also enable the option PKCS# 12 Client Certificates in the Generate Load Test Program menu . The allocation of individual client certificates per simulated user is supported when generating load test programs.
HTTPS Client Certificate Authentication - DER or PEM encoded Files (Proxy Recorder)
Allows to load X509 SSL/TLS DER or PEM encoded client certificates into the proxy recorder. Based on the fact that the proxy recorder operates as "man in the middle" between the Web browser and the Web server, the client certificate must be loaded and activated before a Web surfing session which requires such a certificate can be recorded.
...
Note: To execute a load test which uses client certificates you have additionally to enable the option DER/PEM Client Certificates when generating the Load Test Program. The allocation of individual client certificates per simulated user is supported and can be selected when generating the load test programs.
HTTPS Client Certificate Authentication - PKCS# 11 Device (Proxy Recorder)
Allows to you to use in Proxy Recorder X509 SSL/TLS client certificates which are embedded in PKCS# 11 Security Devices (support for HSMs and smart cards).
...
Because the proxy recorder operates as a man in the middle between the Web browser and the Web server, the client certificate must be loaded and activated before a Web surfing session requiring such a certificate can be recorded.
NTLM Authentication (Proxy Recorder)
Checkbox in Title: If checked, enables NTLM authentication against Web servers during recording.
Note: To execute a load test which uses NTLM authentication, you must also enable the option NTLM Authentication in the Generate Load Test Program menu . The allocation of individual NTLM accounts per simulated user is supported when generating load test programs.
Input Fields
Domain | Windows domain name. | |
Username | Username of domain account. | |
Password | Password of domain account. |
GUI Settings
Input Fields
Time Zone | ¹ Allows you to set the default time zone to be used by the load test programs, and by the GUI. | |
Number Format | ¹ Allows you to set the default decimal grouping separator character for numbers; for example 123’456.00 or 123,456.00. | |
Background Color | Allows you to choose your desired background color for all windows. |
¹ only temporarily applied until program termination - for Windows, Mac OS X and Linux systems: Modify the startup settings file prxsniff.dat to change these values permanently. For other Unix-like systems: Set the program arguments -tz and -dgs to the corresponding values.