Web Detective (Spirent)

Main Menu

News & Events

Buy two or more TracePlus products and save a bundle!

TracePlus Enterprise Bundle.... from $569.95

TracePlus Internet Bundle....from $429.95

TracePlus Pro Bundle....from $359.95

TracePlus Web Development Bundle....from $259.95

TracePlus Software Development Bundle....$289.95

TracePlus®/Web Detective (Spirent Edition) Update

Release Date: 6/15/2007

Version 2.94.000

The patches listed below will only update retail versions of TracePlus®/Web Detective (Spirent Edition).

NOTE: If you are having problems installing the patch over your currently installed version (listed below), follow the following procedure.

Uninstall the product you currently have installed (be sure you have a copy of the original product you purchased).
Reinstall the original version you received when you purchased the product.
Reapply the patch you downloaded from here.

HTTP

FTP

The updater will upgrade the following versions of TracePlus/Web Detective (Spirent Edition):

TracePlus/Web Detective (Spirent Edition) v2.35.000
TracePlus/Web Detective (Spirent Edition) v2.50.000
TracePlus/Web Detective (Spirent Edition) v2.51.000
TracePlus/Web Detective (Spirent Edition) v2.60.000
TracePlus/Web Detective (Spirent Edition) v2.62.000
TracePlus/Web Detective (Spirent Edition) v2.63.000
TracePlus/Web Detective (Spirent Edition) v2.64.000
TracePlus/Web Detective (Spirent Edition) v2.65.000
TracePlus/Web Detective (Spirent Edition) v2.67.000
TracePlus/Web Detective (Spirent Edition) v2.68.000
TracePlus/Web Detective (Spirent Edition) v2.69.000
TracePlus/Web Detective (Spirent Edition) v2.70.000
TracePlus/Web Detective (Spirent Edition) v2.71.000
TracePlus/Web Detective (Spirent Edition) v2.80.000
TracePlus/Web Detective (Spirent Edition) v2.83.000
TracePlus/Web Detective (Spirent Edition) v2.85.000
TracePlus/Web Detective (Spirent Edition) v2.86.000
TracePlus/Web Detective (Spirent Edition) v2.90.000
TracePlus/Web Detective (Spirent Edition) v2.91.000
TracePlus/Web Detective (Spirent Edition) v2.92.000

The patch includes all bug fixes up to 6/15/2007. We recommend that you apply this patch so that TracePlus®/Web Detective (Spirent Edition) can operate at its maximum efficiency.

To apply the patch, unzip this file to a temporary directory and run SETUP.EXE from Windows.

If you cannot find the version number of your product in this list, or the update does not work with your product, please e-mail for a new copy of SETUP.EXE.

Please note that in order to receive a new copy of SETUP.EXE, you must provide us with a copy of the original SETUP.EXE from your purchased copy of the product.

Version History

Version 2.94.000 of TracePlus®/Web Detective (Spirent Edition) includes the following fixes or enhancements:

Drag and drop applications and documents from the Windows Desktop, Start Menu, and folders onto the application main window in order to launch them from TracePlus. (NEW)

Version 2.92.000 of TracePlus®/Web Detective (Spirent Edition) includes the following fixes or enhancements:

The capacity of the Protocol View has been increased to 9,000 records. (NEW)
Capacity of the Cookies View has been increased to 9,000 records. (NEW)
Capacity of the Data View has been increased to 35,000 lines. (NEW)
Reading files previously generated by TracePlus may cause the application to crash due to incorrect size information recorded for compressed and chunked packets. (FIXED)
The Server Usage View would appear empty when reading a file previously generated by TracePlus. (FIXED)

Version 2.91.000 of TracePlus®/Web Detective (Spirent Edition) includes the following fixes or enhancements:

HTTP and HTTPS communications may not be captured as expected because of previous changes to the API hooking technology used by TracePlus. (FIXED)

Version 2.90.000 of TracePlus®/Web Detective (Spirent Edition) includes the following fixes or enhancements:

The base technology used to intercept Winsock and WININET APIs has been been updated for more stability and speed. (NEW)
The Setup application was modified to install certain TracePlus menu items under the "All Users" directory which means that they will appear for all user accounts on the PC. Note that this feature can only be obtained by requesting a new SETUP.EXE from the Support department. (NEW)
Updated to create, read, and write certain necessary files under limited user accounts.. (NEW)
The buffer size of the Protocol View and Cookie View has been increased to 8,000 records. (NEW)
Increased the maximum number of viewable lines in the Data View from 15,000 to 20,000. (NEW)
SSL data may not display as expected when an applications closes a WININET connection handle. (FIXED)Objects whose HTTP response does not contain a "Content-Length" field may not be captured in their entirety. (FIXED)
Objects with the content type "gzip" or "deflate" would be decompressed up to maximum of 65535 bytes. (FIXED)
Certain SSL enabled sites would not be captured as expected. This problem is seen particularly when the "Remote IP Resolution" feature is disabled. (FIXED)
Patch updater would not patch properly licensed products due an error in checking for a digital signature in previous versions of the product. (FIXED)
An application may crash when intercepted by TracePlus while running on a HyperThreaded CPU (Intel processors only) on Windows XP or Windows 2003 Server. (FIXED)
SSL requests and responses may not appear when using an application via a proxy server and the "Remote IP Resolution" option is unchecked. (FIXED)
RTSP objects were being tracked and accumulated in the Object View and Page View. This was not intended behavior and has been disabled. (FIXED)
Updates of the summary line for one or more pages in the Page View may cause TracePlus to crash due to a threading issue. (FIXED)
Sizes of objects appearing in the Object View included the size of the HTTP response header. (FIXED)
Sizes of objects appearing in the Page View included the size of the HTTP response header. (FIXED)
Problems with Winsock 2 implementation caused data to be missing or out of sequence. Particularly effects .NET applications but can affect any application using Winsock 2 and GetQueuedCompletionStatus(). (FIXED)
Incorrect parsing of chunked data may cause objects to display incorrectly or not at all in the Object View and Page View. (FIXED)
Some third party Browser Helper Objects were passing invalid parameters to certain WININET functions causing Internet Explorer to crash when TracePlus referenced the parameter. (FIXED)Certain types of domain resolution calls made via the getaddrinfo() API may cause the target application to crash in certain circumstances on Windows XP and Windows 2003 Server. (FIXED)
Newer versions of the Java Runtime Environment would pass an incorrect parameter to the Winsock connect() API causing memory corruption and termination of the target application. (FIXED)
Certain Browser Helper Objects would pass an invalid parameter to InternetConnect() and InternetOpenURL() causing memory corruption and termination of the target application. (FIXED)
The IP Address "2.0.0.0" may appear in various Views during SSL connections due to an issue handling domain name requests via getaddrinfo() when running Windows XP or Windows 2003 Server. (FIXED)
The socket number appearing in the Data VIew as part of an SSL connection may be interpreted as a socket number instead of a WININET handle. (FIXED)
The Excluded Process Names list on the "More Filters' tab does not reset as expected when a new filter is loaded. (FIXED)
Removed the prompt to debug child processes since there already is a checkbox for enabling this feature on the Launch Tab of the Capture Settings dialog box.
The demo dialog box would display when specifying an application on the TracePlus command line (only in demo versions of the product). (MODIFIED)
The demo dialog box would display when launching a service with TracePlus (only in demo versions of the product). (MODIFIED)
When clicking on an .WDV file in Windows Explorer, it would be ignored if TracePlus was already running. (FIXED)Incorrect interpretation of calls to getaddrinfo() may result in empty addresses appearing in the DNS Lookup View. (FIXED)

Version 2.86.000 included the following fixes or enhancements:

Large POST requests can be implemented in Avalanche Scripts by the automatic insertion of POST_DATA variables. The files referenced by the POST_DATA variable will be created automatically in the same directory as the script. (NEW)

Version 2.85.000 included the following fixes or enhancements:

The URL column in the Object View now includes any parameter information specified in the request URL. (NEW)
The URL column in the Page View now includes any parameter information specified in the request URL. (NEW)
HTTP protocol element help can now be accessed in the Protocol View from the Header, Header+Body, and Body Content views. (NEW)
HTTP protocol element help can now be accessed in the Object View from the Request, Response, and Body Content views. (NEW)
HTTP protocol element help can now be accessed in the Page View from the Request, Response, and Body Content views. (NEW)
Enhancements to the core API interception technology provide greater compatibility with applications running on all Windows platforms. (NEW)
An application may crash when intercepted by TracePlus while running on a HyperThreaded CPU (Intel processors only) on Windows XP or Windows 2003 Server. (FIXED)
SSL requests and responses may not appear when using an application via a proxy server and the "Remote IP Resolution" option is unchecked. (FIXED)
Updates of the summary line for one or more pages in the Page View may cause TracePlus to crash due to a threading issue. (FIXED)

Version 2.83.000 included the following fixes or enhancements:

RTSP methods and responses made by streaming media objects are now displayed in the Protocol View. (NEW)
Sizes of objects appearing in the Object View included the size of the HTTP response header. (FIXED)
Sizes of objects appearing in the Page View included the size of the HTTP response header. (FIXED)
Problems with Winsock 2 implementation caused data to be missing or out of sequence. Particularly effects .NET applications but can affect any application using Winsock 2 and GetQueuedCompletionStatus(). (FIXED)
Incorrect parsing of chunked data may cause objects to display incorrectly or not at all in the Object View and Page View. (FIXED)
Some third party Browser Helper Objects were passing invalid parameters to certain WININET functions causing Internet Explorer to crash when TracePlus referenced the parameter. (FIXED)

Version 2.80.000 included the following fixes or enhancements:

Added a new menu item "View Online FAQ" to the Help menu. This will launch the default browser with the URL of a new Frequently Asked Questions page containing information on how to use the product. (NEW)
Random timing errors would occur when running TracePlus on a dual-processor PC or a PC with a dual-core CPU. (FIXED)
Browser Automation Scripts did not work due to invalid parsing of the command line passed to TracePlus. (FIXED)
Browser Automation Scripts may not execute correctly because of faulty DDE communications with Internet Explorer. (FIXED)
Specifying /START, /STOP, or /RESUME within a Browser Automation Script would not update the toolbar in the main window as expected. (FIXED)
Certain applications such as Java Applets launched from a Web Browser may terminate unexpectedly. (FIXED)
Start times and elapsed times may be incorrect if the source of data resulted from a call to GetQueuedCompletionStatus(). (FIXED)
Memory leaks may occur in the target application because of errors in cache reporting logic. (FIXED)
FIxed an issue where newer versions of the Java Runtime Environment pass an incorrect parameter to the Winsock connect() API causing memory corruption and termination of the target application. (FIXED)
FIxed an issue where certain Browser Helper Objects pass an invalid parameter to InternetConnect() and InternetOpenURL() causing memory corruption and termination of the target application. (FIXED)
Script objects were not being written when .WDV files were created. This means that files transported to another workstation could not generate a script after loading the .WDV file. (FIXED)
Certain HTTP requests containing a parameter list separator other than "?" (question mark), would cause incorrect port numbers to appear when a script is generated. (FIXED)
The IP Address "2.0.0.0" may appear in various Views during SSL connections due to an issue handling domain name requests via getaddrinfo() when running Windows XP or Windows 2003 Server. (FIXED)
The splash screen logo would display when TracePlus was launched as a result of double-clicking on a .WDV file in Windows Explorer. (FIXED)
The splash screen logo would display when launching a service with TracePlus. (FIXED)
The splash screen logo would display when TracePlus was launched using a Browser Automation script. (FIXED)
Child processes would not be debugged as expected. (FIXED)
Launching TracePlus with an application specified on the command line would not launch the application. (FIXED)

Version 2.71.000 included the following fixes or enhancements:

The Server Usage tab in the Data View displayed total bytes for both sent and received data for a specific IP address instead of total received bytes only. (FIXED)
When accumulating total bytes for the Server Usage tab in the Data View, fast CPUs may cause garbage information to appear in the graph. (FIXED)
The Cookies View would sort incorrectly if the sort column was anything but the first column. (FIXED)
Further enhancements to Winsock 2 API support. (UPDATED)

Version 2.70.000 included the following fixes or enhancements:

TracePlus now works correctly with HTTP and SSL traffic through HTTP 1.1 compliant proxies. (NEW)
A "Reload Cached Objects" option has been added to the View menu. When checked, Internet Explorer will request all objects from the server whether or not they exist in the cache. You can use this feature instead of clearing the Internet Explorer cache. (NEW)
The functionality of the Start button has been changed so that you can push the Start button at any time to launch another application while a capture is already started. (NEW)
When running in a Terminal Server or Remote Desktop session, the default window position assigned by Windows will be used instead of the saved window position. (NEW)
The process of intercepting applications launched from Windows Explorer has been modified so that changing directories within an Explorer view will not cause the "Do you want to trace" prompt to appear. (NEW)
Launching applications from shared directories on remote PCs would not cause the "Do you want to trace" prompt to appear. (FIXED)
The retail version of the product would limit Avalanche scripts to a certain number of lines as in the demo version. This is incorrect as the retail version supports an unlimited number of lines in an Avalanche script. (MAJOR FIX)
Viewing SSL traffic may cause Internet Explorer to hang unexpectedly due to code added recently to improve handling of redirects. This code was not necessary and has been removed. (FIXED)
Streaming video from sites such as ESPN or CNN may playback incorrectly while running inside TracePlus. (FIXED)
Applications using Winsock the 2 API (particularly overlapped I/O and completion ports) would result in packets being processed out of order or not at all. (FIXED)
Certain Web servers such as IBM WebSphere may send chunked size values one byte at a time, causing TracePlus to prematurely terminate parsing of that object. (FIXED)
Headers containing "Transfer-Encoding: chunked" but not any data after the HTTP header may cause a crash . (FIXED)
The "Include single byte packets" option in the Data View tab of the Capture Settings dialog box has been removed because single byte packets may be processed as part of an HTTP method or response. (FIXED)
The Packet Options displayed in the Data View tab of the Capture Options dialog box incorrectly stated that up to 8192 bytes would be displayed, although 4096 bytes were actually displayed. (FIXED)

Version 2.65.000 included the following fixes or enhancements:

The ";" character has been added as a valid indicator of query parameters, so parameters following ";" will be parsed out and displayed correctly. (NEW)
The "@" character has been added as a valid indicator of query parameters, so parameters following ";" will be parsed out and displayed correctly. (NEW)
The rightmost "/" character followed by "parameter=value" is now recognized as a valid indicator of query parameters, so parameters following "/" will be parsed out and displayed correctly. (NEW)
Added support for values contained in multipart/form-data sections for the Spirent Edition. Note that file uploads and "Content-Type" directives in MIME sections are not supported. (NEW)
A progress bar now appears when saving Headers as ASCII. (NEW)
A progress bar now appears when saving Requests as ASCII. (NEW)
A progress bar now appears when saving as an Avalanche Script. (NEW)
The object names appearing in the Object View and Page View would sometimes contain query or fragment information. (FIXED)
A breakpoint was mistakenly left in the code which triggered on a specific URL. (MAJOR FIX)
Incorrect parsing of an object name could cause TracePlus to crash. (MAJOR FIX)
Updating socket connection information may cause an application to crash due to multithreading issues. (FIXED)
Certain sequences of compressed headers would not be parsed correctly and do not appear in the Protocol View. (FIXED)
Certain sequences of chunked headers would not be parsed correctly and do not appear in the Protocol View. (FIXED)
Attempts were made to write scripts to disk when the script feature was not active. (FIXED)
Port numbers appearing in Avalanche scripts may be inaccurate due to incorrect parsing of the HTTP request. (FIXED)
Extraneous character string ":u" would randomly appear in Avalanche scripts before the port number. (FIXED)
Requested objects that return a 4xx response with a Content-Type field would assume the role of the specified type, i.e. a graphical object would appear in an Avalanche script as a Level 1 URL instead of a Level 2 URL. (FIXED)
The Help file has been updated to reflect the most recent updates to the Toolbar.

Version 2.63.000 included the following fixes or enhancements:

Cookies displayed in the Header tab of the Protocol View are now displayed using a bold font, for easier reading.
The port number of the server is displayed after the IP address in the Connect Times View.
Fixed a problem where TracePlus would crash with an access violation on startup if DEP support was enabled in Windows XP SP2 and Windows 2003 Server SP1. This problem is most likely to occur on PCs with AMD Athlon 64 Family processors, as well as newer Intel Xeon, Pentium 4, Pentium M or "Centrino" processors, and Celeron-D processors. (MAJOR FIX)
Fixed an issue where the Object View displayed incorrect information because the target browser was communicating through a proxy server. (FIXED)
Fixed an issue where the Page View displayed incorrect information because the target browser was communicating through a proxy server. (FIXED)
Incorrect URLs would appear in a generated Avalanche script when the target browser was communicating through a proxy server. (FIXED)
Duplicate objects would appear in the Object View when password protected pages were encountered and HTTP 401 Not Authorized responses were received. (FIXED)
Duplicate objects would appear in the Page View when password protected pages were encountered and HTTP 401 Not Authorized responses were received. (FIXED)
Duplicate objects would appear in a generated Avalanche script when password protected pages were encountered and HTTP 401 Not Authorized responses were received. (FIXED)
There was a bug in calculating the final compression ratio displayed on the summary line of each page in the Page View. (FIXED)
Port numbers would not be displayed next to IP addresses in the Cookies View, Data View, Object View, and Page View if the URL specified in the browser was raw IP address (i.e. http://192.168.1.x/test.html). (FIXED)
When printing any chart, the printer you specified via the Print Setup dialog box would not used. Instead the Windows default printer would always be selected. (FIXED)

Version 2.60.000 included the following fixes or enhancements:

Added an Expires column to the Page View. (NEW)
Modified the Ratio column in the Object View and Page View to display values commonly associated with a ratio, i.e. "3.02:1", "1:1", etc.. (NEW)
Added option to the Launch Tab of the Capture Settings dialog box which enables the capturing of applications launched from a command prompt (NT 4.x/2000/XP only). (NEW)
Added option to the Launch Tab of the Capture Settings dialog box which disables the capturing of child processes spawned from the target process. (NEW)
Performance enhancements show a noticeable increase in execution speed for target applications. (NEW)
Fixed an issue where objects included on a base page such as Javascript were incorrectly identified as pages, causing succeeding objects to appear in the wrong page on the Page View. (FIXED)
Fixed an issue where objects in the Page View that failed with a 40x or 50x series error code were not displayed in red. (FIXED)
Fixed an issue with the Ratio column in the Object View and Page View where if the compressed size was larger than the actual size, a incorrect value would appear, i.e. "(1).235".(FIXED)
Fixed an issue with the Body Contents display in the Page View where selecting a Summary record would display the previously selected object instead of a blank display. (FIXED)
Fixed an issue with the IE Cache display in the Page View where selecting a Summary record would display the previously selected object instead of a blank display. (FIXED)
Fixed an issue with the IE Cache display in both the Object View and Page View where cache information after the HTTP response was not updated correctly. (FIXED)
Fixed an issue with the Validate Links dialog where Web sites requiring authentication would display as inaccessible. An authentication dialog should appear (unless Internet Explorer is configured for automatic authentication). (FIXED)
Fixed an issue with the Validate Links dialog where Web sites on non-HTTP port numbers could not be traversed. (FIXED)
Fixed an issue with the Web Performance dialog where Web sites requiring authentication would display as inaccessible. An authentication dialog should appear (unless Internet Explorer is configured for automatic authentication). (FIXED)
Fixed an issue with the Web Performance dialog where Web sites on non-HTTP port numbers could not be traversed. (FIXED)
The Time to First Byte column in the Page View would display 0.000000 in the page summary line instead of the average TTFB time for all objects. (FIXED)

Version 2.51.000 included the following fixes or enhancements:

IP addresses are displayed with the appropriate DNS names in any View that displays IP addresses. (NEW)
Increased the maximum number of records in the Cookie View from 6000 to 7500 records. (NEW)
Modified the View in Browser feature to utilize three different browser types (Internet Explorer, Netscape Navigator, and Mozilla) instead of the default browser. (NEW)
Added an Edit Object feature to the Object View and Page View which launches a downloaded object in the appropriate editing application. Use the Set Editing Applications dialog box in the Edit Menu to specify a default editor if not configured in Windows. (NEW)
Added an Export Object feature to the Object View and Page View which saves a downloaded object to disk in the appropriate format. (NEW)
Added a Request view to the Page View which displays the HTTP request for a selected object. (NEW)
Added a Response view to the Page View which displays the HTTP response for a selected object. (NEW)
Added a Cache Information Viewer to the Object View. The Cache View determines whether an object exists in the Internet Explorer Cache before the object is requested from the server. If the object is in the cache, the information about that object will be reported in the column labeled "Before Request". After the response for the object has been received, it is then determined whether Internet Explorer has added or updated the object in its cache. If the object is in the cache, the information about that object will be reported in the column labeled "After Response". Note that this feature works with Internet Explorer only (NEW)
The Activation Wizard now offers three ways to activate your product: Direct (via the Internet), e-Mail, and via our Web site. (NEW)
The DNS Lookup view columns have been rearranged with the Requested time column appearing first.
POST methods may not appear in the generated script. (FIXED)
The Save as ZIP file and Stream to Disk using the Create Zip file option did not work as expected. (FIXED)
The Time to First Byte column in the Page View would display 0.000000 in the page summary line instead of the average TTFB time for all objects. (FIXED)
Enabling the Display Packet Size feature in the Data View would use two lines in the Data View instead of a single line. (FIXED)
HTTP responses with the status code 302 were causing an HTML object entry in the Object View and Page View. (FIXED)

Version 2.35.000 included the following fixes or enhancements:

Files created by version 2.30.000 would be corrupted and do not load due to invalid data in IE cache structures. Note that files created by version 2.30.000 cannot be repaired, however newly created files will not have this problem. (MAJOR FIX)
When running .NET applications under Windows 2000 and Windows XP using .NET Framework 1.1, HTTP responses would not be seen by TracePlus. (FIXED)
HTTP sessions would not display correctly if a web application was using overlapped I/O or I/O completion ports. (FIXED)

Version 2.30.000 included the following fixes or enhancements:

Connection emulation feature converts capture timings to emulate end-user network connections such as dialup modems, DSL modems, and cable modems. (NEW)
Attach comments to any item in the Protocol View, Cookie View, DNS Lookup View, Connect Times View, Object View, and Page View. (NEW)
Filter information based on port number i.e. HTTP, HTTPS, or up to four user-specified port numbers. See the Filters tab on the Capture Settings dialog box. (NEW)
Filter information based on an IP address or IP address mask. Up to 20 IP addresses or masks can be specified. See the Filters tab on the Capture Settings dialog box. (NEW)
Filter the processes being intercepted by TracePlus by specifying up to 15 process names that will not be intercepted by TracePlus. See the Filters tab on the Capture Settings dialog box. (NEW)
Modified the Image View in the Protocol View, Object View, and Page View to display text objects as well as graphical objects. The Image View has been renamed the Body Contents View. (NEW)
Find the next comment in a View. (NEW)
Delete a single comment or all comments in a View. (NEW)
Improved microsecond timing accuracy. (NEW)
Increased the maximum number of records in the Protocol View from 6000 to 7500 records. (NEW)
Added Relative Time column to the Protocol View. (NEW)
Added the ability to save a capture loaded from disk a second time (useful when adding comments to already existing capture file. (NEW)
Copying over 3000 items to the clipboard in all views would take a significant length of time. (FIXED)
When exiting the application, you may be prompted twice to save the capture. (FIXED)

Version 2.28.000 included the following fixes or enhancements:

Some compressed objects received from the server would not be decompressed as expected. (FIXED)
Attempts to import files from Web Detective (Standard Edition) version 3.85.xxx and higher would fail with the error "Cannot load this RDF file". (FIXED)
Files imported from the Web Detective (Standard Edition) version 3.85.xxx and higher support the display of images, however the Spirent Edition would not display them. (FIXED)
Object View records imported from the Web Detective (Standard Edition) version 3.85.xxx and higher were not converted correctly, causing display problems in the Object View. (FIXED)
The Save Headers as ASCII feature in the Protocol View would not write out complete headers if the file was imported from the Web Detective (Standard Edition). (FIXED)
The Save Requests as ASCII feature in the Protocol View would not write out complete headers if the file was imported from the Web Detective (Standard Edition). (FIXED)
The Packed value displayed in the Object View would be zero if the file was imported from the Web Detective (Standard Edition) (FIXED)
The Packed value displayed in the Page View would be zero if the file was imported from the Web Detective (Standard Edition) (FIXED)
The Packed value displayed in the Page View would be zero if the file was imported from the Web Detective (Standard Edition). (FIXED)
Increased number of objects displayed in Top Objects by Size graph to 200 objects.(NEW)
Increased number of objects displayed in Top Objects by Time graph to 200 objects.(NEW)

Version 2.26.000 included the following fixes or enhancements:

HTTP response headers that specify Transfer-Encoding: Chunked when in reality the data was not chunked might cause TracePlus to crash. (FIXED)
The additional support of compressed objects caused a corruption of a variable which would cause WDV files to be written incorrectly to disk or TracePlus would abort the save procedure with an error message (version 2.25.000 only). (MAJOR FIX)
Support for BCOPY, BDELETE, BMOVE, BPROPFIND, BPROPPATCH, and X-MS-ENUMATTS methods available in Microsoft Exchange Server 2000/2003. (NEW)
The Expired field in the Object View and Page Summary View are now calculated based Added a "Packed" and "Ratio" column headings to the Page View. These columns will show the effect that compressed content-encodings have on the downloaded object. Ratio is expressed as a percentage change between the "Packed" value and the "Size" value. The Summary line will contain an average of these two columns. (NEW)
Added a "Cache" column to the Object View. This value represents the caching status of the object derived from scanning the HTTP response headers. There are four states: yes (cacheable), no (not cacheable), private, no-cache, and expired. (NEW)

Version 2.20.000 included the following fixes or enhancements:

Support for HTTP headers with either "deflate" and "gzip" content encodings. Headers will be decompressed by TracePlus and displayed in their original format. (NEW)
Added a "Packed" and "Ratio" column headings to the Object View. These columns will show the effect that compressed content-encodings have on the downloaded object. Ratio is expressed as a percentage change between the "Packed" value and the "Size" value. (NEW)
Added a "Packed" and "Ratio" column headings to the Page View. These columns will show the effect that compressed content-encodings have on the downloaded object. Ratio is expressed as a percentage change between the "Packed" value and the "Size" value. The Summary line will contain an average of these two columns. (NEW)
Added a "Cache" column to the Page View. This value represents the caching status of the object derived from scanning the HTTP response headers. There are four states: yes (cacheable), no (not cacheable), private, no-cache, and expired. (NEW)
Added a Cache Information Viewer to the Object View. The Cache View determines whether an object exists in the Internet Explorer Cache before the object is requested from the server. If the object is in the cache, the information about that object will be reported in the column labeled "Before Request". After the response for the object has been received, it is then determined whether Internet Explorer has added or updated the object in its cache. If the object is in the cache, the information about that object will be reported in the column labeled "After Response". Note that this feature works with Internet Explorer only (NEW)
Added the an Image Viewer to the Protocol View. This permits viewing of graphical objects downloaded as HTTP responses in the following formats: BMP, GIF, ICO, JPG/JPEG, PCX, PNG, TIFF, and WMF. (NEW)
Added the an Image Viewer to the Object View. This permits viewing of graphical objects appearing in the Object View in the following formats: BMP, GIF, ICO, JPG/JPEG, PCX, PNG, TIFF, and WMF. (NEW)
Added the an Image Viewer to the Page View. This permits viewing of graphical objects appearing in the Page View in the following formats: BMP, GIF, ICO, JPG/JPEG, PCX, PNG, TIFF, and WMF. (NEW)
An issue with IIS 6.0 causes the server to send headers with the Transfer-Type set to chunked, while the body is actually in gzip or deflate format. (FIXED)

Version 2.18.000 included the following fixes or enhancements:

(All charts) If a small number of objects (less than 7) was displayed in a chart, the object names would not be aligned with the bar to the right of the object name. (FIXED)
(All charts) Changed style of charts to "3D", and enabled horizontal gridlines. (NEW)
The Print option in the Protocol View, Object View, Page View, and Data View would be enabled if the view contained zero records. (FIXED)
Added several MIME types that will display as ASCII in the Header+Body View, Object Request View, and Object Response View:
- application/x-www-form-urlencoded
- any MIME type beginning with "application/xml"
- application/x-javascript
- any MIME type beginning with "application/x-httpd-php"
The Save Requests as ASCII option did not include POST information from the body of the packet. (FIXED)
Removed the POST information size limitation from the Save as Avalanche format (previously 4096 characters). (FIXED)
Header information for HTTP responses with a status code of 100 were not saved, therefore the response could not be displayed in the Header+Body View. (FIXED)

Version 2.16.000 included the following fixes or enhancements:

Added several MIME types that will display as ASCII in the Header+Body View, Object Request View, and Object Response View: application/x-www-formurlencoded, application/xml-(any value), application/x-javascript, and application/x-httpd-php(any value).
The Save Requests as ASCII option did not include POST information from the body of the packet. (FIXED)
Removed the POST information size limitation from the Save as Avalanche format (previously 4096 characters). (FIXED)
Header information for HTTP responses with a status code of 100 were not saved, therefore the response could not be displayed in the Header+Body View. (FIXED)
Added Save Headers as Script option, which saves a script in Spirent Avalanche format with full request headers (Spirent Edition only). (NEW)
Added Save Headers as ASCII option, which saves HTTP headers as a tab delimited file in the sort order specified by the Protocol View. (NEW)
Added Save Requests as ASCII option, which saves HTTP requests as a tab delimited file in the sort order specified by the Protocol View. (NEW)
The following options on the Launch page of the Capture Options dialog box: "Launch specified application" and the command line parameters specified for that application were not remembered when saving a filter profile. (FIXED)
The following options on the Settings page of the Capture Options dialog box: "Minimize when started", "Stop capture when activated", and "Always on top" were not remembered when saving a filter profile. (FIXED)
The "Always on top" option on the Settings page of the Capture Options dialog box did not work. (FIXED)
The "Disable application debugger detection" feature defaults to unchecked (turned OFF), should be checked by default (turned ON). (FIXED)
The demo version of the product would crash due to a invalid pointer being passed to a memory allocation function. (FIXED)
A blank entry would be added to the list of applications in the Launch tab of the Capture Options dialog when the Start button was pressed. (FIXED)
SSL enabled URLs specified using IP addresses instead of domain names may be missing when a script is generated (Spirent Edition only). (FIXED)
The DNS Lookup View would not detect domain lookups via WsaAsyncGetHostByName(), thus appearing empty when running Netscape Navigator or Opera browsers. (FIXED)
An error when intercepting the Winsock function accept() may cause the target application to crash or not work as expected. (FIXED)
Removed two DebugBreak() statements which under certain specific situations will cause TracePlus to generate a exception. (FIXED)
The international date, time, and numeric formatting can be reset to English (United States) by selecting "Use English (U.S.) Formatting" from the View menu. This feature is enabled only if the user locale specified in Windows is other than English (United States), i.e. France, Germany, etc.. (NEW)

Version 2.10.002 included the following fixes or enhancements:

Supports the date, time, and numeric formats of over thirty countries:

Australia	France	New Zealand
Austria	Germany	Norway
Belgium	Iceland	Paraguay
Bolivia	Indonesia	Philippines
Brazil	Ireland	Portugal
Canada	Italy	South Africa
Chile	Jamaica	Sweden
Colombia	Liechenstein	Switzerland
Denmark	Malaysia	United Kingdom
Finland	Mexico	Venezuela

(NEW)

Alternate SSL port numbers specified in the Settings tab of the Capture Options dialog box were being ignored (except for port 443). (FIXED)
Now compatible with .NET Web Services, ASP.NET, HTML Applications (HTAs), .NET Remoting, and applications written for the .NET Framework (SSL under .NET is not supported at this time). (NEW)
The Clear Internet Explorer Cache option on the View menu did not clear the cache as expected. (FIXED)
When using Browser automation scripts: The /IE_CLEARCACHE option did not clear the IE cache as expected. (FIXED)

Version 2.07.000 included the following fixes or enhancements:

Single packet headers containing no "Content-Length" field may not appear in the Protocol View until the socket closes. (FIXED)
A fix appearing in version 2.06.000 may result in objects with no request or response headers. This will occur when response headers do not contain a "Content-Length" field, and multiple HTTP requests are sent on the the same socket number. (FIXED)
When saving a capture in WDV format, if there are objects in the file with no request or response headers (see above problem) then TracePlus will crash when loading the file. (FIXED)
In the Object View, selecting View as Hex for the Request View would only affect the currently displayed request. When a different object is selected, the View will revert to View as ASCII, while the View as Hex button on the toolbar stays selected. (FIXED)
In the Object View, selecting View as Hex for the Response View would only affect the currently displayed request. When a different object is selected, the View will revert to View as ASCII, while the View as Hex button on the toolbar stays selected. (FIXED)
When using Browser automation Scripts: The /RESUME command acts as the /START command and starts a new instance of the current application, rather than resuming the capture. (FIXED)
When using Browser automation Scripts: The /RESUME command will not reopen the log files, therefore information will not be written to the log files after the /RESUME command is issued. (FIXED)

Version 2.06.000 included the following fixes or enhancements:

SSL responses displayed by TracePlus may have been cached by Internet Explorer on your system drive. TracePlus now displays these cached items in a brown color in all Views. (NEW)
The "Stream to Disk" feature(s) would cause the output file to be corrupted when used on a fast PC (1.6 GHZ) or greater) due to a multi-threading problem. This feature was entirely rewritten. (FIXED)
The "Stream to Disk" feature(s) would not write the file header when TracePlus was paused and subsequently terminated. The output file would then be unreadable by TracePlus. (FIXED)
An error in reading WDV files was discovered which may erroneously omit reading the last record in the file. (FIXED)
The "Automatic" and "ASCII" display options in the Data View Settings tab considered characters greater than ASCII 132 as binary, thus either displaying the data in hex or not displaying it at all. The range considered as ASCII characters has been expanded to ASCII 32-255, thus including international characters. (FIXED)
The Web Performance dialog box would crash when long URLs were typed into the URL combo box, and the Start button was pressed. (FIXED)
The Web Performance dialog box did not handle correctly situations where the URL entered into the URL combo box returned an 404 Not Found error. (FIXED)
URLs that contained an ampersand ("&") within a path or filename would be abnormally truncated. (FIXED)
When monitoring an HTTP 1.0 data stream, TracePlus would report object sizes of zero because the "Content-Length" header field was missing. (FIXED)

Version 2.04.000 included the following fixes or enhancements:

The application may crash if the Save as HTML feature was used in any of the Views. (FIXED)
The application may crash if the Save as XML feature was used in any of the Views. (FIXED)
When using the Export feature on the File menu, the file being exported could be moved or copied while the export was in progress, resulting in a file with a corrupted header. (FIXED)
The Header+Body Closeup view displays the Response header instead of the Request header when the highlighted request in the Protocol View is encrypted (SSL).
The Cookie View displays "(response)" in the Method column and incorrect Cookie information in the Cookie column when the HTTP header is encrypted (SSL).
The Header+Body Closeup view displays the Response header instead of the Request header when the highlighted request cookie in the Cookie View is encrypted (SSL).
An error message "Error reading from specified file" may occur when attempting to load a WDV (capture) file.
When printing the Protocol View, the ID column is too wide, the Method/Response column is too narrow, and the Process column is too narrow.
The Print option is missing from the context menu in the Cookies View.
The process ID has added in parentheses to the Process column of the Protocol View.
Several Help topics had broken links.
When using the "Export as ASCII" feature, the application may crash when URLs contained formatting characters recognized by wsprintf().