JDK-6634191 : JRE 6u03 installation failure with HTTP status code=302 error message
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u3
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2007-11-27
  • Updated: 2010-04-04
  • Resolved: 2008-01-15
Related Reports
Duplicate :  
System Environment:
OS: Windows XP Sp2
Browser: IE 7.0

Users trying to install/update JRE 6u03 version from java.com:
receive this error message "An unknown error has been encountered, HTTP status code=302"

What consumers report:
- Im having trouble installing Java version 6 Update 3. When I click on install, I keep getting an error message every time. The message says: An unknown error has been encountered, HTTP status code=302. I have removed my last version of java, and had cleaned out my cookies. Then reboot, and still cant download java"
- "I keep getting HTTP status code=302 and saying I need to download J2SE runtime enviorment 6 update 3".
"My Java needs to be updated, but every time I try to download the program I get this message.  http code=302".
- I cannot download the current version of JAVA. I get the following error message
"An unknown error has occured. HTTP status code = 302"
- I try to down load java and i click the install button and a error message keeps appearing HTTP status code=302

I am not able to reproduce this issue, but this is a regular error message reported by consumers.

Status code 302 dfinition from:

10.3.3 302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field. 

The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s). 

If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. 

Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request.  However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client.

EVALUATION XPI install.js mechanism is now obsoleted by Mozilla.org due to its security prone manner. We are now also obsoleting our use of XPI install.js mechanism for Java download from java.com for FF users. This work is done in 6637304 and has been putbacked to 6u5 b11.

EVALUATION This is part of the on-going XPI download problem from java.com due to Mozilla.org changes in related to support of XPI installation. A few weeks back, the problem is seen only with Vista due to Vista's strict UAC policy. The XPI install.js mechanism (which java.com uses for java installation for firefox/moz users on Windows), is considered a security hole by Mozilla.org. Tracing Mozilla code source, looks like Mozilla.org (Ben Smedberg) has checked in the patch to cease support for XPI install.js on December 4, and Mozilla's PFS server build has now flushed out this change. Since XPI install.js is considered a security issue by Mozilla.org, provided their warning for us a few weeks already, I don't think we can be able to ask them to revert the change to give us more time. This means, no java XPI download on any Windows platform can work anymore. User who gets routed to http://java.com/en/download/index.jsp will receive error when trying to install the XPI bundle. (The current error when I tried on XP is -244: Unsupported package). A plan to move java.com's java installation away from XPI technology has been carried out and is targeted to 6u5. java.com's engineers had been contacted to reroute firefox/mozilla users on windows to manual install page.