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

[mod_curl] Increase argument limit and enforce max args constraint #2727

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

ar45
Copy link
Contributor

@ar45 ar45 commented Jan 14, 2025

Introduced a macro MOD_CURL_MAX_ARGS for the number of arguments for mod_curl functions with a default of 30. Adjusted the code to handle scenarios exceeding this limit by logging an error and returning failure. This improves flexibility and prevents potential overflow issues.

Introduced a configurable limit on the number of arguments for mod_curl functions with a default of 30. Adjusted the code to handle scenarios exceeding this limit by logging an error and returning failure. This improves flexibility and prevents potential overflow issues.
@andywolk andywolk force-pushed the mod_curl_allow_more_argv branch from be7cd61 to e359409 Compare January 14, 2025 23:41
@andywolk andywolk added the bug Something isn't working label Jan 14, 2025
@andywolk andywolk merged commit ad5fe8b into signalwire:master Jan 15, 2025
19 checks passed
@andywolk
Copy link
Contributor

@ar45
Shouldn't argc >= MOD_CURL_MAX_ARGS be argc > MOD_CURL_MAX_ARGS?

@ar45
Copy link
Contributor Author

ar45 commented Jan 15, 2025

@andywolk good catch

Indeed. Since we did char *argv[MOD_CURL_MAX_ARGS + 1]

@andywolk
Copy link
Contributor

Would you like to follow up a PR for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants