JDK-7129311 : Cached gzipped JNLP file should be detected and refreshed by internal usage
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u29,7,8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,windows_7
  • CPU: generic,x86
  • Submitted: 2012-01-12
  • Updated: 2013-09-12
  • Resolved: 2012-01-17
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.
7u4Fixed 8 b22Fixed
Related Reports
Duplicate :  
- Download and install 7u2 JRE.
- Clear cache.
- Run javaws http://www.tumas-project.org/distribution/TUMAS-fx.jnlp once, should see launch error.  This step is just to download the JNLP file and put into cache under gzip format.
- Install unfixed 8 or 7u4-ea b06 and do not clear cache.
- Run javaws http://www.tumas-project.org/distribution/TUMAS-fx.jnlp will see errors unable to launch the app due to gzipped JNLP file in cache was used.

Expecting javaws to detect gzipped format, refresh the cache and launch successfully.

EVALUATION Latest JRE8 b22 could load the test case without exception.But the application would not start.

EVALUATION Method Cache.hasIncompatibleCompressEncoding() has wrong condition limiting check only to jar cache entries.