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

remove Config.MaxRetryTokenAge, set it to the handshake timeout #4064

Merged
merged 1 commit into from
Sep 10, 2023

Conversation

marten-seemann
Copy link
Member

Depends on #4063. For #3549.

There is no good reason to manually set the validity period for Retry tokens. Retry tokens are only valid on a single connection during the handshake, so it makes sense to limit their validity to the configured handshake timeout.

@codecov
Copy link

codecov bot commented Sep 5, 2023

Codecov Report

Merging #4064 (c136f66) into master (e1fcac3) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #4064      +/-   ##
==========================================
- Coverage   83.46%   83.44%   -0.02%     
==========================================
  Files         147      147              
  Lines       14890    14888       -2     
==========================================
- Hits        12427    12422       -5     
- Misses       1967     1970       +3     
  Partials      496      496              
Files Changed Coverage Δ
interface.go 0.00% <ø> (ø)
config.go 100.00% <100.00%> (ø)
server.go 75.93% <100.00%> (ø)

... and 1 file with indirect coverage changes

@marten-seemann marten-seemann changed the base branch from less-magical-connection-timeout to master September 9, 2023 13:13
Copy link
Collaborator

@sukunrt sukunrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no good reason to manually set the validity period for Retry
tokens. Retry tokens are only valid on a single connection during the
handshake, so it makes sense to limit their validity to the configured
handshake timeout.
@marten-seemann
Copy link
Member Author

can remove this too, I think. https://github.com/quic-go/quic-go/blob/master/config_test.go#L83

Done! Thanks for catching this!

@marten-seemann marten-seemann merged commit abfe1ef into master Sep 10, 2023
33 checks passed
@marten-seemann marten-seemann deleted the remove-config-maxretrytokenage branch September 12, 2023 06:24
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.

None yet

2 participants