test case http2/4.2 frame size/3 bugged #142
Description
Test should send HEADERS frame with length > MAX_FRAME_SIZE of server. Instead, it ignores server settings and sends value bigger than 16,384 (i think its from here https://www.rfc-editor.org/rfc/rfc9113.html#section-4.1-4.2.1)
In this output its clear, that for DATA used 8388608 (my valuie from settings + 1), but for headers - 17575, for some reason
✔ 1: Sends a DATA frame with 2^14 octets in length
[send] SETTINGS Frame (length:6, flags:0x00, stream_id:0)
[recv] SETTINGS Frame (length:12, flags:0x00, stream_id:0)
[send] SETTINGS Frame (length:0, flags:0x01, stream_id:0)
[recv] SETTINGS Frame (length:0, flags:0x01, stream_id:0)
[send] HEADERS Frame (length:15, flags:0x04, stream_id:1)
[send] DATA Frame (length:8388608, flags:0x01, stream_id:1)
[recv] WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:0)
[recv] GOAWAY Frame (length:28, flags:0x00, stream_id:0)
✔ 2: Sends a large size DATA frame that exceeds the SETTINGS_MAX_FRAME_SIZE
[send] SETTINGS Frame (length:6, flags:0x00, stream_id:0)
[recv] SETTINGS Frame (length:12, flags:0x00, stream_id:0)
[send] SETTINGS Frame (length:0, flags:0x01, stream_id:0)
[recv] SETTINGS Frame (length:0, flags:0x01, stream_id:0)
[send] HEADERS Frame (length:17575, flags:0x05, stream_id:1)
[recv] WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:0)
[recv] HEADERS Frame (length:5, flags:0x05, stream_id:1)
[recv] Timeout