Customer Problem Description:
-------------------------------
Upon upgrading to JRE 1.4, we noticed an exception in the Java Console that indicated applet caching was failing. The root cause is because our proprietary web server was not returning a LastModified field in its HTTP header responses. We found bug Id 4614095 which indicates this is a "feature" rather then a bug. Note that our applet functions properly, it's just that caching fails.

The relevant portion of the bug report is:

This is not a plug-in bug. I removed the code that was throwing IOException and replaced it with a println message to indicate that some header fields are missing. The plug-in code is doing the right thing and does not cache jar file which does not have lastmodifydate or expiration date.


We would prefer this status be shown as an informational message, and not an IOException, so as not to unduly alarm the user. Is there any way to achieve this with the 1.4 JRE and, if not, can we have such a change in future releases of the plug-in? FYI, we have fixed our web server implementation, but already have a large and diverse deployed base that could take years to upgrade.


###@###.### :
    This bug can be tested with datek account. There is reference to this
account in the bug#4614095