We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Similarly to the ALPN string issue, we define the CONNECTION_CLOSE reason string here as text:
CONNECTION_CLOSE
qlog/draft-ietf-quic-qlog-quic-events.md
Line 313 in 57b6796
The problem here is that RFC 9000 only says the reason string SHOULD be UTF-8. It could be arbitrary, or binary data, even if that is a bad idea.
It should be possible to log a reason string which an implementation sees which does not appear to be valid UTF-8.
The text was updated successfully, but these errors were encountered:
This is related to this implementation issue: openssl/openssl#23807
Sorry, something went wrong.
Agree, I just had to implement this and cast to the bytes to a lossy utf8. Let's make it possible in the spec to capture raw bytes .
Add raw bytes field support to CONNECTION_CLOSE.
d6241e6
Fixes #411
Successfully merging a pull request may close this issue.
Similarly to the ALPN string issue, we define the
CONNECTION_CLOSE
reason string here as text:qlog/draft-ietf-quic-qlog-quic-events.md
Line 313 in 57b6796
The problem here is that RFC 9000 only says the reason string SHOULD be UTF-8. It could be arbitrary, or binary data, even if that is a bad idea.
It should be possible to log a reason string which an implementation sees which does not appear to be valid UTF-8.
The text was updated successfully, but these errors were encountered: