Skip to content

Treat transport error 0x0 correctly in helloquic#276

Open
koflin wants to merge 1 commit intonetsec-ethz:masterfrom
koflin:helloquic-shutdown
Open

Treat transport error 0x0 correctly in helloquic#276
koflin wants to merge 1 commit intonetsec-ethz:masterfrom
koflin:helloquic-shutdown

Conversation

@koflin
Copy link
Copy Markdown

@koflin koflin commented Jun 18, 2025

I've noticed that when running my own SCION QUIC client against the example QUIC server in _examples/helloquic/helloquic.go that when my client closes the connection the server logs an error. Looking closer at the example server implementation I've noticed that the example server does not correctly handle the transport error code 0x0. According to RFC 9000 the transport error code 0x0 means NO_ERROR and can be used to abruptly close the connection. Hence, I think this error code should be ignored by the server and not logged.


This change is Reviewable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant