Name: PK39334
=============
 
Summary:
   Encode the locale information into the redirect URL if the user agent sending the request is identified as a web crawler.
 
Problem Description:
   Portal will send a status code 302 ("Found") when the user agent sending the request is identified as a web crawler and
   the navigational state encoded in the URL is considered to be an "alias" (multiple "URL aliases" may point to the same portal page).
   In order to avoid having the crawler index the same page under different URLs, the redirect status code is sent.
   
   If the URL mapping contains a locale in which the content is to be shown, this information must be encoded into the URL
   sent in the redirect.
   
 
Problem Solution:
   In the PreProcessor the locale was added to the state so that the redirect url includes the selected locale.
   
 
Failing Module(s):
   Engine: URL Generation
 
Affected Users:
   All Users
 
Version Information:
    Portal Version(s): 5.1.0.4
     Pre-Requisite(s): PK28204 
      Co-Requisite(s): ---
 
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 Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   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.
 
Un-Installation:
   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.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.