The HTTP recorder panel enables you to configure the parameters for the recording of an application.
The HTTP Recorder settings group box allows to set the NeoLoad recorder in proxy mode.
Port is the listening port used by the recording proxy.
Capture the browser window even when it is in background (for single window applications) can be selected to have the recorder capture only the HTTP flows going through the browser window used. With this option, it is not necessary to close all the HTTP client applications (web sessions with browsers of other types, Twitter client, and so on) or define exclusion rules to avoid unwanted requests in the recording.
Merge "cookie" keys detected in HTTP/2 header: Ticking the check box allows NeoLoad to merge several "cookie" keys into a single one regrouping all the values. The regrouped values are coma separated. For example, when an HTTP/2 request header contains 3 "cookie" keys with different values for each, the option will merge the "cookie" keys and regroup all the values under a single "cookie "key.
Use NeoLoad to negotiate NTLM and Kerberos tickets (Not compatible with HTTP/2): When an authentication issue occurs through NTLM and/or Kerberos protocols, the option allows NeoLoad to perform the authentication process itself. Before ticking the check box, make sure Kerberos is properly configured in NeoLoad.
Encrypt the passwords detected in forms: Ticking the check box automatically encrypts the value contained in any password-type field during an HTTP recording. By default, the encryption is active.
Certificates used for SSL interception: To capture HTTPS traffic, we implement man-in-the-middle interception. You can either use our self-signed certificate "Embedded NeoLoad Certificate" or browse to your own added as explained just below.
To add your own root certificate
In the Certificates used for SSL interception section, click the "+" button, then browse the to "pkcs12 key" from your file system. NeoLoad then prompts you to enter the password.
Once imported, click the checkmark button to specify that it is the key to be used for SSL interception.
Note: The "-" button allows you to delete a certificate and the 4th button allows you to regenerate the NeoLoad root certificate from the PKCS certificate selected.
The Tunnel Mode Recorder settings group box enables to configure the parameters to record in tunnel mode. For more information, see Record an HTTP application in tunnel mode.
Connection contains the network interface available on the machine. Select the one to be used for the recording in tunnel mode between NeoLoad and the application.
IP accessible from client is the IP used by the tested application to connect to the NeoLoad recorder.
HTTPS IP range recording is the collection of IPs which can be used when recording a number of SSL-secured domains. By default, they are local IPs.
In From, it is necessary to enter the first IP of the collection.
In To, the last IP of the collection must be specified.
In Recorder patterns, the regular expression patterns to filter the URLs to be recorded must be entered in the lists:
Patterns to include: When this list contains an entry, NeoLoad only records the URLs matching at least one regular expression pattern. The Patterns to include list is used only to record requests sent to one or two servers.
Patterns to exclude: The request is recorded when it does not match any of the regular expression patterns in the list. The Patterns to exclude list is used to avoid recording requests sent to certain listed servers, or requests for JAR or image files for example. URLs authorized by the Patterns to include list must pass through the exclude filter, otherwise they are rejected.
All filters consist in regular expressions. It is necessary to escape special characters such as the period. A filter can be, for example, http://windowsupdate\.microsoft\.com. For more information, see Regular expressions.
Information: Regular expressions are applied to the full URL, including URL parameters if any.
