(*** This bug was imported into bugs.kde.org ***) Package: kjava Version: KDE 2.2.1 Severity: normal Installed from: RedHat RPMs Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified I have a Java applet embedded in a page. This page is a JSP page that uses session information to store data for a user on the server. The Java applet itself connects to the same server through HTTP. Its requests should therefore automatically join the same session (like Netscape 4.7x does and the ICE browser). In Konqueror this is not the case which means the applet fails to work correctly. Since this is an applet I've developed myself I can provide all source code and a step by step explanation of how to reproduce the bug. I tried different JVM's starting with Blackdown's 1.3.1 FCS (since that's the most stable with KDE 2) including IBM's 1.3.0 and Sun's 1.3.1 release. They all have the same problem. (Submitted via bugs.kde.org)
Is there any example on the web which developers could use, or is this solved within the current 3.1 series?
Created attachment 974 [details] test web-application deploy this web application on your favourite servlet engine and go to http://<myhost>:<myport>/<mypath>/index.jsp
this is still not solved in KDE_3_1_BRANCH. The problem is that most JSP engines rely on session cookies for their session managment. If cookies are enabled Konqueror receives a session cookie when it accesses the web-application. This cookie is to be used in all subsequent connections back to the server for the same session, including connections made from applets. KJAS does not have access to the cookies maintained by Konqueror (unlike JavaPlugin, which has got access to Mozilla's cookies). Therefore, when the applet sets up its own connection the server creates a new session. I have created a small web-application for testing this behaviour. Install the attached *.war file on your application server (e.g. Tomcat or JBoss) and point your browser at the web-application. A page loads which displays the current session as generated when the page was sent. It also contains an applet that makes its own connection to the server and displays the X-Session-Id header generated by the index.jsp page. Both session Ids should be identical. Mozilla/JavaPlugin handle this correctly, while two different Ids are displayed in Konqueror/KJAS.
*** This bug has been marked as a duplicate of 31903 ***