Logging non-UTF-8 reasons #411
Comments
|
This is related to this implementation issue: openssl/openssl#23807 |
|
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 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similarly to the ALPN string issue, we define the
CONNECTION_CLOSEreason 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: