• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

JSessionID issue

 
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic