-
Bug
-
Resolution: Done
-
Critical
-
34.0.0.Beta1
-
None
-
---
-
---
With EAP 8.0 Update 3.1 we can see failures of 2 tests in the h2spec TS we use to check that the server behaves according to the HTTP2 protocol standard.
Here are the failing tests:
Hypertext Transfer Protocol Version 2 (HTTP/2) 5. Streams and Multiplexing 5.1. Stream States ... using source address 127.0.0.1:35384r sending RST_STREAM frame ร 8: closed: Sends a DATA frame after sending RST_STREAM frame -> The endpoint MUST treat this as a stream error of type STREAM_CLOSED. Expected: GOAWAY Frame (Error Code: STREAM_CLOSED) RST_STREAM Frame (Error Code: STREAM_CLOSED) Connection closed Actual: Timeout using source address 127.0.0.1:35386fter sending RST_STREAM frame ร 9: closed: Sends a HEADERS frame after sending RST_STREAM frame -> The endpoint MUST treat this as a stream error of type STREAM_CLOSED. Expected: GOAWAY Frame (Error Code: STREAM_CLOSED) RST_STREAM Frame (Error Code: STREAM_CLOSED) Connection closed Actual: Timeout
The tests send a RST_STREAM frame and then continue with DATA/HEADERS and expect the server to respond with a GOAWAY. But it never does and the connection just times out instead.
This seems to be brought in by the changes from UNDERTOW-2343
- depends on
-
UNDERTOW-2444 H2 violation of protocol specification in RST_STREAM scenarios
-
- Closed
-
- is incorporated by
-
WFCORE-7030 Upgrade Undertow from 2.3.17 to 2.3.18
-
- Resolved
-
[WFLY-19862] UNDERTOW-2444 - Undertow HTTP2 breaks protocol specification in RST_STREAM scenarios
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Fix Version/s | New: 34.0.0.Final [ 12433719 ] |
Resolution | New: Done [ 1 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Resolution | Original: Done [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Affects Version/s | New: 34.0.0.Beta1 [ 12429943 ] |
Component/s | New: Web (Undertow) [ 12317482 ] | |
Component/s | Original: Undertow [ 12390562 ] | |
Fix Version/s | Original: 27.0.0.Beta1 [ 12430684 ] | |
Fix Version/s | Original: 26.0.1.Final [ 12434163 ] | |
Key |
Original:
|
New:
|
[QE] How to address? | New: --- [ 15567 ] | |
[QE] Why QE missed? | New: --- [ 15561 ] | |
Project | Original: WildFly Core [ 12315422 ] | New: WildFly [ 12313721 ] |
Fix Version/s | New: 27.0.0.Beta1 [ 12430684 ] | |
Fix Version/s | New: 26.0.1.Final [ 12434163 ] | |
Resolution | New: Done [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Component/s | New: Undertow [ 12390562 ] | |
Component/s | Original: Web (Undertow) [ 12317482 ] | |
Key |
Original:
|
New:
|
Affects Version/s | Original: 34.0.0.Beta1 [ 12429943 ] | |
[QE] How to address? | Original: --- [ 15567 ] | |
[QE] Why QE missed? | Original: --- [ 15561 ] | |
Project | Original: WildFly [ 12313721 ] | New: WildFly Core [ 12315422 ] |
Link |
New:
This issue is incorporated by |
Link | New: This issue causes EAPQE-2332 [ EAPQE-2332 ] |
Link |
New:
This issue depends on |
Issue Type | Original: Feature Request [ 2 ] | New: Bug [ 1 ] |
Okay, sorry for the noise - I see it has been upgraded here https://github.com/wildfly/wildfly/commit/df59d59d8fbae98bcf21a6ffa0956e0d53fbeaaa and it is a very recent change. I have run the CI and test no longer fails. I am resolving this.