Skip to content

Advanced Configuration

Most test cases run successfully with Load Tester's automatic configuration: ASM handles dynamic fields, cookies work automatically, DNS resolves normally. This part of the manual covers the rare scenarios where you need manual control over low-level HTTP behavior, network configuration, or browser simulation.

You probably don't need any of this unless you encounter one of these specific problems:

  • JavaScript sets cookies that Load Tester can't capture automatically during recording
  • Application expects browser-specific cookie values (like BROWSERSUPPORT=yes)
  • Internal hostnames don't resolve or need to point to test servers instead of production
  • Proxy server required for network access during recording or replay
  • Load balancer routes by source IP and requires each virtual user to have a unique IP address
  • Captcha blocks automated testing and needs workarounds for performance testing

Before diving in, verify that ASM and the standard configuration wizards can't solve your problem. These techniques are more complex and require careful testing.

The Techniques

  • JavaScript Cookies - Extract a cookie value that client-side JavaScript sets, and re-apply it with a processor.
  • Cookie Config File (cookies.cfg) - Set browser-specific cookie values that can't be extracted from a response, including per-user browser diversity.
  • Hostname Resolution (hosts.txt) - Override DNS, mapping a hostname to a specific IP across the controller and all remote engines.
  • Proxy Settings - Configure, modify, and troubleshoot the proxy used for recording and replay.
  • IP Aliasing - Give virtual users distinct source IP addresses for applications that route or rate-limit by client IP.
  • Captcha Handling - Three cooperative ways to performance-test an application protected by CAPTCHA.

Next Steps

After configuring advanced settings, verify your test case works correctly:

For additional configuration topics:

For reference: