0 Replies Latest reply on Oct 28, 2013 4:02 PM by 4cfce4e7-ba9d-4689-8557-adcc8328a1b3

    JSessionID issue

    4cfce4e7-ba9d-4689-8557-adcc8328a1b3

      We have a JNLP program that makes a REST call to the server during its operations. Without the JNLP we can add the JSESSIONID as a cookie to the REST call and things work just fine.

      But when we make the REST call from the JNLP it adds another JSESSIONID as a cookie and so the original JSESSIONID won’t get picked up. The web application is protected by Spring Security and also all the JARs required for JNLP get’s downloaded correctly and JNLP launched just fine, only the REST call is impacted. We add the following for all jar downloads:

       

      <jar href="lib/log4j-1.2.15.jar;JSESSIONID=<%= request.getSession().getId() %>" />

       

      I would like to either avoid the extra JSESSIONID to add as a cookie or remove the extra JSESSIONID in a Servlet Filter.

      Or any other help to resolve this issue would be greatly appreciate it.

       

      Technology Stack:

      Spring MVC, Hibernate, Spring Security, Tomcat