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.

Sign up for GitHub

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

Jump to bottom

CURLMOPT_MAX_CONCURRENT_STREAMS: make sure the set value is within range #12382

Closed
wants to merge 1 commit into from
Closed

CURLMOPT_MAX_CONCURRENT_STREAMS: make sure the set value is within range #12382

wants to merge 1 commit into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Nov 22, 2023

... or use the default value.

Also clarify the documentation language somewhat.

@bagder
CURLMOPT_MAX_CONCURRENT_STREAMS: make sure the set value is within range
2c49f09 
... or use the default value.

Also clarify the documentation language somewhat.
@bagder bagder added HTTP/2 HTTP/3 h3 or quic related labels Nov 22, 2023
@bagder bagder closed this in 9a8bb20 Nov 22, 2023
@bagder bagder deleted the bagder/multi-max-streams branch November 22, 2023 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
HTTP/2 HTTP/3 h3 or quic related
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@bagder