-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b03
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8299195 | 20 | Christoph Langer | P3 | Resolved | Fixed | b29 |
JDK-8299262 | 17.0.7 | Christoph Langer | P3 | Resolved | Fixed | b01 |
JDK-8299382 | 11.0.19 | Paul Hohensee | P3 | Resolved | Fixed | b01 |
However, older JDKs (e.g. JDK 11) do not populate the body and the test wrongly fails for that reason. It would be better to model the test according to the optional nature of a content body being present or not, without sacrificing assertions the test was meant to do (verify a fix of
[1] https://www.rfc-editor.org/rfc/rfc6455.html#section-5.5.1
- backported by
-
JDK-8299195 WebSockets: HandshakeUrlEncodingTest unnecessarily depends on a response body
-
- Resolved
-
-
JDK-8299262 WebSockets: HandshakeUrlEncodingTest unnecessarily depends on a response body
-
- Resolved
-
-
JDK-8299382 WebSockets: HandshakeUrlEncodingTest unnecessarily depends on a response body
-
- Resolved
-
- links to
-
Commit openjdk/jdk11u-dev/ce106888
-
Commit openjdk/jdk17u-dev/d973531c
-
Commit openjdk/jdk20/92fe304f
-
Commit openjdk/jdk/909d0cb4
-
Review openjdk/jdk11u-dev/1558
-
Review openjdk/jdk17u-dev/958
-
Review openjdk/jdk20/63
-
Review openjdk/jdk/11486