Spectrum OneClick errors with HTTP 403 after upgrading to Java 1.8 Update 202 or greater
search cancel

Spectrum OneClick errors with HTTP 403 after upgrading to Java 1.8 Update 202 or greater

book

Article ID: 126255

calendar_today

Updated On: 09-27-2023

Products

Spectrum

Issue/Introduction

Spectrum OneClick errors with HTTP 403  after upgrading to Java 1.8 Update 202 or greater


java.io.IOException: Server returned HTTP response code: 403 for URL: http://xxx.xxx.xxx.xxx/spectrum/oneclick.jnlp

 

 

Environment

Release: Any
Component: SPCOCK

Cause

For reasons not yet known the newer version of JRE sends out a HEAD request to the OneClick server. The HEAD method is blocked by default as Spectrum was not using this HTTP method.

Resolution

Workaround for this can be implemented on the Server side or via 1 of 2 methods on the client-side.


Via the SERVER SIDE Option

On the OneClick Server
  1. Locate the web.xml file under $SPECROOT/tomcat/webapps/spectrum/WEB-INF/
  2. Make a backup copy of the web.xml file
  3. Edit the web.xml file and search for: <http-method>HEAD</http-method>
  4.   delete the entire line containing the HEAD method
  5.  Save the web.xml file
  6.  Restart the OneClick tomcat process

Note: The web.xml will likely be rewritten to default spec upon upgrading, so it might be necessary to reperform the steps above after the upgrade.


Via the CLIENT SIDE Options ( either or below option)

First Option:


1. Go into Java Control Panel

2. Click the "Settings" button under Temporary Internet Files

3. Uncheck "Keep temporary files on my computer"




4. Click Ok, and then ok again.


The console should now launch successfully.



Second option:


1. Create a new directory on %SYSTEMDRIVE% (I.e. C:\java_cache)

2. Navigate to %SYSTEMDRIVE%/Users/%USERID%/AppData/LocalLow/Sun/Java/Deployment

3. Open the deployment.properties file in a text editor.

4. Add this line:


deployment.user.cachedir=C\:\\java_cache 


5. Save the file and exit.

6. Attempt to start the console


The console should launch.


Either option will work fine.  The second option prevents downloading the Java Application each time it is launched because it will be stored locally.