Name: PK33392
=============
 
Summary:
   HTTPPROXYCONTENTACCESS HANGS ON CERTAIN AUTHENTICATION PROXY SERVERS 401 RESPONSE
 
Problem Description:
   Content Access Service (CAS) can be configured to use specific proxy servers requiring proxy authentication. CAS
   waits for the 401 response from the Proxy before sending the Proxy-Authorization header on the subsequent request. Under some          conditions, the data from the proxy remaining on the Socket causes problems is CAS
 
Problem Solution:
   Resolved stream handling with introduction of ContentLengthInputStream
 
Affected Users:
   All Users using Content Access Service (CAS) and authentication proxy
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): ---
      Co-Requisite(s): ---

 This fix is planned for integration into fix pack 6.0.1

Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The WebSphere® Portal Update Installer (PUI) can be downloaded from the following link:
       http://www.ibm.com/support/docview.wss?rs=688&uid=swg24006942

*Reminder: the version of PUI used varies based on the version of WebSphere Portal.  Ensure the correct version is in use.*

1) Create temporary "fix" directory to store the jar file:
             Unix™: <WP_root>/fix
          Microsoft® Windows®: <WP_root>\fix
2) Copy the jar file to the directory
3) Shut down the WebSphere Portal appserver
4) Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install the fix.
5) Restart WebSphere Portal
6) The temporary directory may be removed.

Directions to remove a fix:

NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
       ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Stop the WebSphere Portal appserver.
2) Follow the instructions that are packaged with the Portal Update Installer on how to uninstall the fix.
3) Restart WebSphere Portal.