tool_getparam: Limit --rate to be smaller than number of ms#12116
Closed
sohomdatta1 wants to merge 1 commit into
Closed
tool_getparam: Limit --rate to be smaller than number of ms#12116sohomdatta1 wants to merge 1 commit into
sohomdatta1 wants to merge 1 commit into
Conversation
Currently, curl allows users to specify absurd request rates that might be higher than the number of milliseconds in the unit (ex: curl --rate 3600050/h http://localhost:8080 does not error out despite there being only 3600000ms in a hour). This PR adds a conditional check before the millisecond calculation making sure that the number is not higher than the numerator (the unit) If the number is higher, curl errors out with PARAM_NUMBER_TOO_LARGE
Contributor
Author
|
In the current tool, the result of the division is zero for numbers higher than the number of ms in the unit, so it doesn't really make sense to keep that case around |
bagder
approved these changes
Oct 14, 2023
Member
|
Thanks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, curl allows users to specify absurd request rates that might be higher than the number of milliseconds in the unit (ex:
curl --rate 3600050/h http://localhost:8080does not error out despite there being only 3600000ms in a hour).This PR adds a conditional check before the millisecond calculation making sure that the number is not higher than the numerator (the unit) If the number is higher, curl errors out with
PARAM_NUMBER_TOO_LARGE