JDK-6822892 : discrepancy in behavior of CachedJarFile.getName() between 160_06 and 160_07
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u12
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2009-03-26
  • Updated: 2010-07-29
  • Resolved: 2009-03-27
Related Reports
Relates :  
JDK-6827175 - fix for 6704074 breaks application unnecessarily
Description
A discrepancy in behavior of CachedJarFile.getName() between 
JRE 1.6.0 Update 6 and JRE 1.6.0 Update 7 was found.

Beginning with JRE 1.6.0_07 function getName() always returns 
an empty string. This was not the case in JRE 1.6.0_06.
Comments
EVALUATION This is not a bug. It's due to security fix: 6704074: localhost socket access due to cache location exposed If they want to read from cache, they can get the inputstream by the JAR URL returned from the JNLPClassLoader, and getInputStream from it. The underlying webstart JARURLConnection will return the contents from the cache.
27-03-2009