JDK-6764338 : when "Range" header is present in HTTP request, we should not cache the request
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-10-28
  • Updated: 2010-09-17
  • Resolved: 2009-02-10
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.
6u12 b01Fixed 7Fixed
When investigating JavaFX bug http://openjfx.java.sun.com/jira/browse/RT-1128, we discovered that "Range" header in HTTP request does not work with the deployment cache.

The current deployment cache is not designed to cache partial "range" resource.

We should not try to cache the resource if range header is present.

EVALUATION fix in 6u12