JDK-4842498 : connection is made to the server regardless of the cache_version parameter
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.1
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-04-03
  • Updated: 2003-04-07
  • Resolved: 2003-04-07
Related Reports
Duplicate :  
Description

Name: gm110360			Date: 04/03/2003


FULL PRODUCT VERSION :
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

FULL OS VERSION :
Microsoft Windows 2000 [Version 5.00.2195]

EXTRA RELEVANT SYSTEM CONFIGURATION :
Server is IIS or Apache2

A DESCRIPTION OF THE PROBLEM :
When using "cache_version" to control cached jar invalidation, a connection to the server is made even though the cache_version indicates that the cached version is valid.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. set javaplugin.trace=true in Java Plug-in Control Panel
2. use the following script to download any applet

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
  <head>
    <title>Java 2D(TM) Demo</title>
  </head>

  <body>
	<OBJECT myscript classid = "clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
    		width="100%" height="100%" align="baseline" name=Java2Demo
    		codebase="http://java.sun.com/products/plugin/autodl/jinstall-1_4_1-windows-i586.cab#Version=1,4,0,0">
		<PARAM NAME="code" VALUE="java2d.Java2DemoApplet.class">
		<param name="cache_archive" value="Java2Demo.jar">
		<param name="cache_version" value="1.4.0.1">
		<param name="type" value="application/x-java-applet;version=1.4">
	</OBJECT>
  </body>
</html>

3. Quit the browser and load the same applet again, see the trace

EXPECTED VERSUS ACTUAL BEHAVIOR :
connection to the server should not be made on the second applet load
connection to the server is made on every start of the applet

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
It seems that setting expiration date of content on the server, eliminates the problem
(Review ID: 182744) 
======================================================================