Name: PK27203
=============
 
Summary:
   Base tag causes URL to contain wrong protocol in special setups
 
Problem Description:
   In security environments using a different protocol between browser and Web server than between Web server and portal server, the base tag (activated on WP 5.1.0.3 by default) causes URLs to contain the wrong protocol.
   For example, in environments using a SSL connection between browser and Web server and a non-SSL connection between Web server and portal server, the base tag will contain an absolute URL starting with "http" instead of "https". Therefore all relative URLs contained in the markup are served using the URL of the HTML base tag with the wrong protocol.
   Note that on WP 5.1.0.2 this problem can only occur if APAR PK15894 is installed.
 
Problem Solution:
   Fix makes sure that the base tag is not enabled by default because the portal server does not know whether or not there is a secure SSL connection established between browser and Web server. The base tag can be re-activated by setting the config setting com.ibm.wps.engine.tags.StateBaseTag = true in  <portal-server>/shared/app/config/services/ConfigService.properties.
    
 
Failing Module(s):
   Engine: Tags & Commands
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): 
      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.