JDK-6963653 : Losing session cookie with Java 6.0u18 and Next Gen plugin
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Affected Version: 6u18
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- OS: windows_xp
- CPU: x86
- Submitted: 2010-06-23
- Updated: 2010-09-14
- Resolved: 2010-06-29
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
When opening a URL in a new window via AppletContext.showDocument(), the session cookie is no longer passed over to the new window when Next Gen plugin is enabled. Note, the applet is in an iframe. This behavior is observed in JRE 1.6.0_18 running in IE 6 and IE7. The problem did not exist in any previous version of the JRE, including both 1.5 and 1.6. Expected Result: When the applet is loaded, the pop up shows the cookies in this page. There should be 3 cookies: 1.Permanent cookie that was added by the applet.html 2.Session cookie that was added by servlet code 3.Jession cookie We expect to see all three cookies passed to the target page -- showCookie.html Actual Result: When user clicks on the applet, and showCookie.html is displayed in new browser window the second cookie is missing. (IE 6 and IE 7 Only) Frequency: Always We had the same code since JRE 1.4 and never had this problem before. This works with JRE 1.6.0_17
Comments
|