url: change default value for CURLOPT_MAXREDIRS to 30#11581
Closed
url: change default value for CURLOPT_MAXREDIRS to 30#11581
Conversation
It was previously unlimited by default, but that's not a sensible default. While changing this has a remote risk of breaking an existing use case, I figure it is more likely to actually save users from loops.
icing
approved these changes
Aug 2, 2023
ptitSeb
pushed a commit
to wasix-org/curl
that referenced
this pull request
Sep 25, 2023
It was previously unlimited by default, but that's not a sensible default. While changing this has a remote risk of breaking an existing use case, I figure it is more likely to actually save users from loops. Closes curl#11581
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.
It was previously unlimited by default, but that's not a sensible default. While changing this has a remote risk of breaking an existing use case, I figure it is more likely to actually save users from loops.
The curl tool already sets a limit on its own, so that will not be affected by this.