Quic triggering an "Unsupported setting:" warning when processing a recieved response #241
Replies: 1 comment 1 reply
-
The settings id is included to test that the peer ignores unknown frames. The spec says:
h3 applies this setting here: https://github.com/hyperium/h3/blob/34bf403bad8893adc0363e45a74782828aa93ac8/h3/src/config.rs#L106C1-L106C67 |
Beta Was this translation helpful? Give feedback.
-
I am using your example code for client server quic connection. Both sides of the connection trigger the warning with different setting ids, which the code randomly generates. I am trying to figure out what setting or other item in the received frame that would be triggering this warning.? I included the code and warning I receive from each side.
Client:
Tracer Output:
Server:
Tracer Output:
Beta Was this translation helpful? Give feedback.
All reactions