Softpedia >Mac >Utilities >Proxy Sniffer >  Changelog

Proxy Sniffer Changelog

What's new in Proxy Sniffer 5.2-M

Mar 25, 2015
  • NEW FEATURES:
  • Load Test Arguments Stored in Result Files:
  • All arguments of a load text job are now stored in the result file (*.prxres file). You can review the arguments of a job in the "Load Test Result Detail" menu "Test Scenario".
  • Support of TLS 1.2 and SNI added:
  • TLS 1.2 and SNI (Server Name Indication) is now supported by ProxySniffer and enabled by default.
  • Debugging of SSL/TLS Handshakes Option added t"Personal Settings" Menu:
  • SSL/TLS Handshakes can now debugged during the recording of a Web surfing session by enabling the corresponding (new) option in the "Personal Settings" menu. The debug information is written tstdout, or respectively tthe ProxySniffer Console. Note: Debugging of SSL/TLS Handshakes for executed load test programs is already fully supported since Version 5.2-H.
  • Debugging of Outbound TCP/IP Connections for Proxy Recorder added:
  • Outbound TCP/IP connections of the Proxy Recorder can now debugged by passing the ProxySniffer startup argument -debugRecorderSocketPools
  • DNS, TCP/IP and SSL Information added for each Recorded URL:
  • DNS resolve time (only if an OS-independent DNS configuration for the Proxy Recorder is used) SourceTCP/IPaddress
  • SourceTCP/IPportnumber
  • TargetTCP/IPaddress
  • TargetTCP/IPportnumber
  • SSL session Id (for encrypted HTTPS URL calls only)
  • Support of DNS Translation File added:
  • A "DNS Translation File" is a DNS configuration file (similar tthe DNS hosts file), that contains on each line a translation between twDNS names. If the first DNS name in the file match tthe DNS name that is passed tthe DNS resolver then the second DNS name is used tresolve the IP address.
  • The first DNS name can alscontain one or more wildcard characters ('*' = wildcard for multiple characters, '?' = wildcard for single character). Lines or a part of a line can be commented out by using the hash char '#'.
  • For recording Web surfing sessions you can configure this option by passing the ProxySniffer startup argument -dnstranslation , or alternatively, you can configure this option alsin the prxsniff.dat configuration file (all options have tbe set in this file at the same, single line). The "DNS Translation File" can alsconfigured on the fly by using the Proxy Recorder REST API.
  • When executing a load test program you can configure this option by entering -dnstranslation intthe "Additional Options" input field. You have tZIP the DNS translation file together with the compiled class of the load test program.
  • Note 1: It could be needed that TLS SNI (Server Name Indication) must be disabled if a DNS translation file is used.
  • Note 2: The HTTP request header field "Host" is not updated, sit might happen that you call the Web server with the wrong host name.
  • Debugging of DNS Cache and DNS Resolves added:
  • For recording Web surfing sessions you can configure the debugging of the DNS cache and its resolves by passing the ProxySniffer startup argument -debugDNS, or alternatively, you can configure this option alsin the prxsniff.dat configuration file (all of the options have tbe set in this file at the same, single line). The debug information is written tstdout, or respectively tthe ProxySniffer Console.
  • When executing a load test program you can configure this option by entering -dnsdebug intthe "Additional Options" input field. The debug information is written tthe stdout file (*.out) of the load test job.
  • New: Support for "Recorder Plug-Ins" added:
  • Proxy Sniffer “Recorder Plug-ins” are Extension Modules tthe Proxy Sniffer product and can be automatically executed during the recording of a Web surfing session. Furthermore, “Recorder Plug-ins” can alsmanually called from the Web Admin GUI or called from the Proxy Recorder REST API.
  • Such Recorder Plug-Ins have direct access tthe recorded session data and alstthe internal “Var Handler” which means that such Plug-Ins can modify HTTP Request and Response data before, during and after the recording, and that such Plug-Ins can alscreate variables, variable extractors and variable assigners. Furthermore such plug-ins can alsreconfigure the HTTP response “content test” settings of URL calls.
  • The main purpose for using Recorder Plug-Ins is tautomate some parts of the post-processing steps – after a session has been recorded. Another purpose is tmodify HTTP request data during recording on the fly – just before they are sent tthe Web server.
  • Detailed information about "Recorder Plug-Ins" is available in the new PDF document Recorder Plug-In Developer Handbook.
  • New Functions tthe Proxy Recorder REST API added:
  • Clear the DNS resolve cache GettheDNStranslationmap
  • SettheDNStranslationmap
  • Getoutlineinformationaboutall“RecorderPlug-Ins”
  • Change the state of a “Recorder Plug-In” tactive or tinactive Manually call a “Recorder Plug-in”
  • Triggerare-scanfor“RecorderPlug-Ins”
  • DISCONTINUED FUNCTIONS:
  • Selecting "SSL V2" as a SSL protocol option has been removed
  • Kerberos authentication has been removed

New in Proxy Sniffer 5.2-E (Sep 19, 2014)

  • Optimization for Large Clusters of Load Generators:
  • The startup-speed when launching cluster jobs have been substantially increased (up to 20 times faster).
  • Additionally, the stability for large clusters of load generators that contain many hundreds of cluster members (Exec Agents) has been improved.

New in Proxy Sniffer 5.1-C (Jan 27, 2014)

  • Support for "Reverse Proxy" Web Traffic Recording:
  • The recording Proxy Server program is normally started as a standard outbound HTTP(S) proxy. Unlike to that, as a special option, it's now also supported to operate the recording Proxy Server program as a "Reverse Proxy" – meaning as an upstream server in front of a Web server. However, when using this special option, you can record HTTP or HTTPS traffic for only one (target) Web server. Further information about this new option is available at the revised "Application Reference Manual", chapter 3.1.1 "Starting Proxy Sniffer as a Reverse Proxy / Special Option".
  • Using Multiple Client IP-Addresses / New IP-Address per Executed Loop:
  • Using multiple client IP-Addresses at the load generators is supported since long time by configuring the load test argument
  • -multihomed. But the available client IP-Addresses have always been distributed across the simulated users. In addition it's now also supported:>
  • to distribute the available client IP-Addresses across the executed "Loops" – irrespective of which simulated user executes a "Loop". This new behavior can be achieved by combining the following both load test arguments: -multihomed -ipperloop
  • Sort Options in "Jobs" Menu added:
  • The list of the load test jobs displayed in the "Jobs" menu can now be sorted, and in reverse order sorted, by "cluster name" + "job date", by "job ID", by "job state" + "job date", by "job date", and by "load test program" + "job date".
  • Housekeeping for Exec Agents and Job Controller added:
  • A configuration free internal housekeeping thread has been integrated in the Exec Agent(s) and in Job Controller that search at regular intervals for corrupt jobs (corrupt job directories) and deletes the corrupt job data. The integrated housekeeping is automatically started when starting an Exec Agent or the Job Controller and can be debugged by using the program argument –debugHousekeeping
  • Executor’s Annotation of Load Test Jobs can be Modified at Runtime:
  • The “Executor’s Annotation” (a small description about the purpose why executing the current load test job) can now modified/updated in the GUI at runtime during the execution of a job. The same functionality is also implemented at command line level as a new PrxJob command.
  • Java System Properties of Load Test Jobs can be Modified at Runtime:
  • All of the Java System Properties of a load test job can now be modified (added/deleted/updated) in the GUI at runtime during the execution of a job. Furthermore, modifications of Java System Properties at cluster-job-level are also supported by the GUI. The same functionality is also implemented at command line level as new PrxJob commands.
  • Automatic Detection of Insufficient Java Memory for Load Test Jobs added:
  • The Java memory consumption, as well the total processing time of the Java garbage collector, is now permanently measured during the execution of each load test job (inside the load test job). This information is transferred at real time to the GUI which compares the Java-internal measuring data with configurable thresholds. If such a threshold is exceeded then the GUI display an alert message about “Low Java Memory” – at job level as well as at cluster-job-level.

New in Proxy Sniffer 5.0-P (Jun 13, 2013)

  • New Functions and Features:
  • Support for DNS configuration "per load test Job" has been added.
  • Configurable File Path for Definitions-Files about Load Generators and Cluster of Load Generators has been added.
  • Additional Features / Updated:
  • Overriding of the User-Agent when starting a load test program has been added.
  • The additional DNS option -dnsstatistic has been added that can be used when starting a load test.
  • Support of Multiple IP Addresses and Load Balancing for outbound TCP/IP connections has been added for the Internal Communication from the WebAdmin and JobController components to the Exec Agents.