Patch Version:	2.8.3.0200.13

Product:		Intel NetStructure 7140 Traffic Director  
			Intel NetStructure 7140 Traffic Director  Export Version
			Intel NetStructure 7145 Traffic Director  
			Intel NetStructure 7145 Traffic Director  Export Version
			Intel NetStructure 7170 Traffic Director  
			Intel NetStructure 7170 Traffic Director  Export Version	
			Intel NetStructure 7175 Traffic Director  
			Intel NetStructure 7175 Traffic Director  Export Version	
			Intel NetStructure 7180 e-Commerce Director  
			Intel NetStructure 7180 e-Commerce Director  Export Version	
			Intel NetStructure 7185 e-Commerce Director  
			Intel NetStructure 7185 e-Commerce Director  Export Version

Release Date:	11/06/01

Fix Details:    CR004775: rich_app does not work with custom methods
			with Content-Length
		When custom HTTP methods are used, rich_app does not
		forward additional data if it is received in a separate
		packet although Content-length is specified in the HTTP
		header.  This change modifies rich_app to always check
		for Content-length and forward additional data
		associated with any POST, PUT or custom HTTP method.
		This change affects Layer 7 services only.

		CR004876: RICH does not insert Connection: close header
			in HTTP/1.1 connections
		When a request is received without the "Connection:
		Keep-alive" or "Connection: close" directive in the 
		HTTP header, rich_app does not insert it into the
		header prior to forwarding the request to the
		fulfillment server.  With HTTP/1.1, the default action
		is "Connection: Keep-alive".  Layer 7 services do not
		support HTTP Keep-alive connections, and the results of
		subsequent requests may be unsuccessful.  This change 
		modifies rich_app to always insert the "Connection:
		close" directive in the HTTP header prior to forwarding
		the request.

		CR004972: rich_app parse for "Content-length" string
			starts after end of buffer
		This issue is related to CR004775.  When searching for
		the "Content-length:" directive in the HTTP header, the
		parser incorrectly initialized the search of the
		request buffer and searched outside of the buffer.
		This occasionally caused rich_app to find the string
		when the request did not include additional data.
		This caused the client browser to hang.  This change
		confines the search to the request buffer correctly.
		This change only applies to Layer 7 services.

		CR005850: Need to disable SSH1 support
		This change removes support for SSH1 and the NULL 
		cipher to prevent potential security problems.

Installation Instructions:
1)  Download the patch install file to a local ftp server. 

2)  Verify that the device is currently booted to a valid boot index
	for patch installation.  This patch can only be installed on
	release 2.8.3.x.13 for the same product with a patch version
	less than 0200.

Note:	If this patch is installed on an incorrect release, the
	"config sys software install" command may report that the
	image has been installed, but the new boot index will not be
	shown with the "config sys software info" command. 

3)  Save the current policygroup configuration to a save filename
	(not default.cfg).
Note:	This is a precautionary measure.  A manual restore of the
	configuration will only be necessary if the current running
	configuration fails to restore normally after booting to 
	the new boot index.

4)  Install the patch install file file using the CLI "config sys
	software install" command or the GUI Update Software facility.

5)  Verify the newly installed boot index is available for boot.

6)  Boot to the newly installed boot index.

7)  Verify the policygroup configuration has restored normally.