-
Bug
-
Resolution: Fixed
-
P3
-
5.0
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2139496 | 5.0u10 | Chris Hegarty | P2 | Resolved | Fixed | b01 |
FULL PRODUCT VERSION :
Java HotSpot(TM) Client VM 1.5.0_07-b03
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
We have an client/server application consisting of an applet which communicates with a servlet. In order to manage the session, the JSESSIONID cookie transmitted by the serlvet in the Set-Cookie response header is set as a cookie using the setRequestProperty API.
This worked in all previous JREs including 1.5.0_06.
Probably the fix for 2132633 (or 6360774) is reponsible for this regression.
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 5.0u6
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
Java HotSpot(TM) Client VM 1.5.0_07-b03
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
We have an client/server application consisting of an applet which communicates with a servlet. In order to manage the session, the JSESSIONID cookie transmitted by the serlvet in the Set-Cookie response header is set as a cookie using the setRequestProperty API.
This worked in all previous JREs including 1.5.0_06.
Probably the fix for 2132633 (or 6360774) is reponsible for this regression.
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 5.0u6
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
- backported by
-
JDK-2139496 Sending "Cookie" header with JRE 1.5.0_07 doesn't work anymore
-
- Resolved
-
- causes
-
-
- Resolved
-