url: Use UTF-8 conversion for Windows Unicode libidn builds#7256
Closed
jay wants to merge 1 commit intocurl:masterfrom
Closed
url: Use UTF-8 conversion for Windows Unicode libidn builds#7256jay wants to merge 1 commit intocurl:masterfrom
jay wants to merge 1 commit intocurl:masterfrom
Conversation
- For Windows Unicode builds of libcurl that use libidn, attempt to convert the hostname from UTF-8 and if that fails use local encoding as a fallback. Prior to this change Windows Unicode builds that use libidn attempted to convert the hostname from the local encoding only. The curl tool passes the command-line URL (and therefore the hostname) in Unicode's UTF-8 encoding, so the conversion would fail. Since other applications may pass locally encoded URLs to libcurl we'll keep local encoding as a fallback. Reported-by: dEajL3kA@users.noreply.github.com Assisted-by: Viktor Szakats Fixes curl#7228 Closes curl#7246 Closes #xxxx
Member
|
My comment here: #7246 (comment) |
Member
Author
|
Closing in favor of #7257 |
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.
convert the hostname from UTF-8 and if that fails use local encoding
as a fallback.
Prior to this change Windows Unicode builds that use libidn attempted to
convert the hostname from the local encoding only. The curl tool passes
the command-line URL (and therefore the hostname) in Unicode's UTF-8
encoding, so the conversion would fail. Since other applications may
pass locally encoded URLs to libcurl we'll keep local encoding as a
fallback.
Reported-by: dEajL3kA@users.noreply.github.com
Assisted-by: Viktor Szakats
Fixes #7228
Closes #7246
Closes #xxxx