APAR status
Closed as program error.
Error description
ESI always returns 200 response with content body whenever cache
does not hit, even if client supplied valid IMS header. I think
that ESI should compare an date in Last-Modified-header from
appserver and removed-IMS-header before sending a response back
to client.
Local fix
N/A
Problem summary
****************************************************************
* USERS AFFECTED: Websphere 5.0 plug-in users of ESI caching *
* processor. *
****************************************************************
* PROBLEM DESCRIPTION: When ESI caching is enabled, for any *
* requests with If-Modified-Since *
* header, plug-in always sends back 200 *
* response. However, when *
* Last-Modified time is not later than *
* If-Modified-Since time, 304 status *
* should be sent. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
200 status code was sent back where 304 should be sent.
Problem conclusion
This problem happened because the Last-Modified response
header was not processed correctly. That has been corrected.
Temporary fix Comments
APAR information |
APAR number |
PQ81909 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-12-09 |
Closed date |
2004-01-30 |
Last modified date |
2004-01-30 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|