Fix (APAR): PK98225 Status: Fix Release: 7.0.0.7, 7.0.0.5, 7.0.0.3 Operating System: AIX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: n/a Byte size of APAR: 54,076 Date: 2009-10-26 Abstract: Cache responses with s-maxage set NOTE!: If the PK96410 interim fix is also going to be applied, then it should be installed prior to installing this fix. Description/symptom of problem: PK98225 resolves the following problem: ERROR DESCRIPTION: The mod_cache IBM HTTP Server module does not cache responses with the Cache-Control: s-maxage directive set, particularly when the requests have query parameters. The module correctly caches responses with the Cache-control max-age directive. The s-maxage directive is used to direct shared or intermediary caches to cache content on behalf of the origin server. This is particularly useful when you do not want the browser caches to cache the same content. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: IBM HTTP Server 7.0 users that are using mod_cache. PROBLEM DESCRIPTION: Some responses that could have been cached were not being cached, resulting in possible lower performance. RECOMMENDATION: Apply this fix if using mod_cache with IHS 7.0. IBM HTTP Server was not considering Cache-control: s-maxage in response headers when making cacheability decisions. This could result in responses that could have been cached, not being cached. PROBLEM CONCLUSION: Worked with Apache development to fix the problem in open-source Apache, then ported the agreed-on fix to IBM HTTP Server. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE!: If the PK96410 interim fix is also going to be applied, then it should be installed prior to installing this fix. The user must: * For V6, have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * For V7, logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * For V6, be at V6.1.0.13 or newer of the Update Installer and for V7, be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205400 Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension. 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory. 2) Stop IBM HTTP Server 3) Launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination. 9) For V7, all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 10) Restart IBM HTTP Server Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * 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 IBM HTTP Server 2) Start Update Installer 3) Enter the installation location of the IBM HTTP Server. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart IBM HTTP Server Directions to re-apply fix: 1) Stop IBM HTTP Server. 2) Follow the Fix instructions to apply the fix. 3) Restart IBM HTTP Server. Additional Information: