Closed
Conversation
Contributor
|
|
Used for extracting: - when used asking for a scheme, it will return CURLUE_NO_SCHEME if the stored information was a guess - when used asking for a URL, the URL is returned without a scheme, like when previously given to the URL parser when it was asked to guess - as soon as the scheme is set explicitly, it is no longer internally marked as guessed The idea being: 1. allow a user to figure out if a URL's scheme was set as a result of guessing 2. extract the URL without a guessed scheme 3. this makes it work similar to how we already deal with port numbers Extend test 1560 to verify. Closes #13616
49ec9a4 to
acfdf96
Compare
vszakats
added a commit
to vszakats/hb
that referenced
this pull request
Jan 23, 2025
Upcoming in curl v8.9.0. Ref: curl/curl#13616
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
2 participants
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.
Used for extracting:
when used asking for a scheme, it will return CURLUE_NO_SCHEME if the stored information was a guess
when used asking for a URL, the URL is returned without a scheme, like when previously given to the URL parser when it was asked to guess
as soon as the scheme is set explicitly, it is no longer internally marked as guessed
The idea being:
allow a user to figure out if a URL's scheme was set as a result of guessing
extract the URL without a guessed scheme
this makes it work similar to how we already deal with port numbers
Extend test 1560 to verify.