fix(utils): handle 1xx HTTP status codes in curl utils#1540
Merged
deathbeam merged 1 commit intoCopilotC-Nvim:mainfrom Mar 29, 2026
Merged
fix(utils): handle 1xx HTTP status codes in curl utils#1540deathbeam merged 1 commit intoCopilotC-Nvim:mainfrom
deathbeam merged 1 commit intoCopilotC-Nvim:mainfrom
Conversation
Update the curl utility to treat 1xx (informational) HTTP status codes, such as 100 (Continue), as non-errors in both GET and POST requests. Previously, only 2xx (success) codes were considered valid, which could cause issues with streaming or intermediate responses. This change improves compatibility with APIs that use informational status codes. Closes CopilotC-Nvim#1508
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
1 participant
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.
Update the curl utility to treat 1xx (informational) HTTP status codes,
such as 100 (Continue), as non-errors in both GET and POST requests.
Previously, only 2xx (success) codes were considered valid, which could
cause issues with streaming or intermediate responses. This change
improves compatibility with APIs that use informational status codes.
Closes #1508