Nim 2.x support and replace std/httpclient with puppy#10
Merged
Conversation
beshrkayali
changed the title
beshrkayali
added a commit
that referenced
this pull request
Jun 2, 2026
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.
std/httpclienton modern Nim rejects WebDAV's custom verbs (PROPFIND,MKCOL,MOVE,COPY) with "Invalid HTTP method name" before any network call because the HttpMethod enum has no WebDAV verbs and there's no public API to send a custom one. This broke ls/props/mkdir/mv/cp on Nim >= ~1.6 (#7) .This PR switches the transport to puppy which sends arbitrary verbs and handles TLS/redirects via the OS HTTP stack. puppy is synchronous, so the client is now synchronous too (BREAKING change).