-
Bug
-
Resolution: Fixed
-
P3
-
6, 6u23, 7, 8, 9
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2205020 | 6-pool | Unassigned | P3 | Closed | Won't Fix |
When a resource has a query string, such as "foo.jar?param=value1" is cached, the reasource is cached based soley on the noQuery href "foo.jar", so when the query string changes (such as "foo.jar?param=value2", additional resources are not cached.
But if a resource URL has parameters such as "foo.jar;jsessionid=1234", it is cached based on the whole URL, so that if referenced again as "foo.jar;jsessionid=5678", another instance of foo.jar is cached.
This is a regression from 1.5.0
But if a resource URL has parameters such as "foo.jar;jsessionid=1234", it is cached based on the whole URL, so that if referenced again as "foo.jar;jsessionid=5678", another instance of foo.jar is cached.
This is a regression from 1.5.0
- backported by
-
JDK-2205020 Cache: resources with parameters such as foo.jar;jsessionid=123456 are multiply cached
- Closed
- duplicates
-
JDK-7011540 Javaws should ignore sessionid and parameters in the url and treat as same application when caching
- Closed
- relates to
-
JDK-6439638 Calls to Applet.getImage( URL ) fail to reflect changes in the URL's content.
- Resolved
-
JDK-6734197 Caching of the jnlp file with query string fails
- Closed