JDK-4837340 : Cache versioning fails to work in 1.4.1 and higher releases
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.1
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_2000
  • CPU: generic,x86
  • Submitted: 2003-03-25
  • Updated: 2003-12-02
  • Resolved: 2003-08-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other
1.4.1_07 07Fixed 1.4.2_02Fixed
Related Reports
Duplicate :  
JDK-4842498 - connection is made to the server regardless of the cache_version parameter
Description
Even when cache version are specified for jar files, plug-in connects to the server to get the time stamp and last modified date
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.1_07 1.4.2_02 generic tiger FIXED IN: 1.4.1_07 1.4.2_02 tiger INTEGRATED IN: 1.4.1_07 1.4.2_02 tiger VERIFIED IN: 1.4.1_07 1.4.2_02
14-06-2004
EVALUATION Too late for mantis, committing to tiger ###@###.### 2003-03-25 The initialized CachedJarLoader is not used if the version check is passed. Because of this, the caching code results in timestamp check even if the required version is on the user system. ###@###.### 2003-07-14
14-07-2003