support a must: prefix for gets #336
Merged
Conversation
This file contains 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
Normally a missing component just causes a blank output. This currently does not work "scheme" (it defaults to the "guessed" scheme). "must:" deos not return error if query/fragment was there but empty (this latter part requires libcurl 8.8.0 or later. The feature is named 'get-empty' in the version output.) Added tests Closes #336
bagder
force-pushed
the
bagder/must-component
branch
from
7d1a23a
to
5e3d94a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
using a
must:prefix for gets makes trurl return error for missing partsIf libcurl is new enough a present but zero-length query or fragment does not cause an error when
must:is used.