Skip to content
New issue

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

#3000: Serialize debug_data when present in GOAWAY frames #673

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

Herbstein
Copy link
Contributor

@Herbstein Herbstein commented Apr 14, 2023

Fixes hyperium/hyper#3200

Debug data in GOAWAY frames is opaque information meant for diagnostic purposes. The data was previously read and stored when being received, but was never written during encoding.

This pull request includes the data when encoding the frame but does not add a (stable) way of setting the data. If it is desired I am happy to include it too. I suspect the function added for testing purposes wouldn't be fit for a stable, public API.

Additionally, I've included an integration test as described in the original issue. However, I'm quite sure there is a better way of creating the GOAWAY frame, I'm just not familiar enough with the structure of the integration tests to find it at the moment. With a few pointers I'd like to rewrite how it is done, if needed.

@seanmonstar seanmonstar merged commit 072f7ee into hyperium:master Apr 25, 2023
@Herbstein Herbstein deleted the 3200-serialize-debug-data branch April 25, 2023 10:29
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.

Add internal serialization of debug_data to HTTP/2 GOAWAY frames
2 participants