quic: Bump maximum history length, make configurable #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@timwoj / @ckreibich - would like to get that into 6.1. This is the change in the spicy-quic repo that in a second step would be cherry-picked into the Zeek tree after rewriting (or so my approach currently). Mind approving? @dopheide-esnet shared a breakdown of the history field and there were many variations capped at 10 characters. |
timwoj
approved these changes
Oct 20, 2023
awelzel
deleted the
topic/awelzel/longer-but-configurable-history-max-length
branch
awelzel
added a commit
to zeek/zeek
that referenced
this pull request
Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.