Is there any interaction between applets and their hosting browser when making HTTP requests, or are requests made completely independently of native browser code?
Specifically, do Java applets running in a browser have some implicit way of sharing the browser’s session state and cache?
I’ve read a few posts from non-authoritative sources saying that when an applet makes an HTTP request that it will use the browser’s cache, and that it will also have access (somehow) to the browser’s cookies.
Tests I’ve done using URLConnection suggest that this is not the case, and my gut feeling is that it sounds far too convenient to be true. I would assume that nothing in the JVM knows anything about the world outside of that JVM, meaning the only other way this could work would be if the JVM implementation is specific to the browser its implementation of the URL-related methods delegate to native browser code?
If cookie data is not implicitly shared or available, is best practice to pass a session ID in a param tag to the applet? Are there security concerns with this approach? If the applet doesn’t use the browser’s cache for requests, how does caching requests in an applet work?
My testing with Windows 7, Java 1.6.23 and Firefox, Chrome and Internet Explorer is that
HttpURLConnections from within an applet’s JVM interact in no way with the browser. They don’t use the cache, and don’t have cookie headers added.