curl/tests/data/test2046, branch gemini-meta cURL mirror with patches applied tests: set LC_ALL in more tests 2019-12-19T22:01:14+00:00 Daniel Stenberg daniel@haxx.se 2019-12-19T15:44:07+00:00 b4c9982382469398115cc0e3e0747e79db083455 Follow-up to 23208e330ac0c21 Closes #4743 
Follow-up to 23208e330ac0c21

Closes #4743
tests: use consistent environment variables for setting charset 2017-02-25T14:33:29+00:00 Dan Fandrich dan@coneharvesters.com 2017-02-23T20:47:17+00:00 c6ddb606d8a3fdbe89763f7299e7f43cf6581567 The character set in POSIX is set by the locale defined by (in decreasing order of precedence) the LC_ALL, LC_CTYPE and LANG environment variables (CHARSET was used by libidn but not libidn2). LC_ALL is cleared to ensure that LC_CTYPE takes effect, but LC_ALL is not used to set the locale to ensure that other parts of the locale aren't overridden. Since there doesn't seem to be a cross-platform way of specifying a UTF-8 locale, and not all systems may support UTF-8, a <precheck> is used to skip the test if UTF-8 can't be verified to be available. Test 1035 was also converted to UTF-8 for consistency, as the actual character set used there is irrelevant to the test. This patch uses a different UTF-8 locale than the last attempt, namely en_US.UTF-8. This one has been verified on 7 different Linux and BSD distributions and is more complete and usable than the locale UTF-8 (on at least some systems). 
The character set in POSIX is set by the locale defined by (in
decreasing order of precedence) the LC_ALL, LC_CTYPE and LANG
environment variables (CHARSET was used by libidn but not libidn2).
LC_ALL is cleared to ensure that LC_CTYPE takes effect, but LC_ALL is
not used to set the locale to ensure that other parts of the locale
aren't overridden.  Since there doesn't seem to be a cross-platform way
of specifying a UTF-8 locale, and not all systems may support UTF-8, a
<precheck> is used to skip the test if UTF-8 can't be verified to be
available.  Test 1035 was also converted to UTF-8 for consistency, as
the actual character set used there is irrelevant to the test.

This patch uses a different UTF-8 locale than the last attempt, namely
en_US.UTF-8. This one has been verified on 7 different Linux and BSD
distributions and is more complete and usable than the locale UTF-8 (on
at least some systems).
Revert "tests: use consistent environment variables for setting charset" 2017-02-24T07:41:36+00:00 Daniel Stenberg daniel@haxx.se 2017-02-24T07:41:36+00:00 13314ffd65c5b7386d041be8111b90e1d150e117 This reverts commit ecd1d020abdae3c3ce3643ddab3106501e62e7c0. That commit caused test failures on my Debian Linux machine for all changed test cases. We need to reconsider how that should get done. 
This reverts commit ecd1d020abdae3c3ce3643ddab3106501e62e7c0.

That commit caused test failures on my Debian Linux machine for all
changed test cases. We need to reconsider how that should get done.
tests: use consistent environment variables for setting charset 2017-02-23T22:14:00+00:00 Dan Fandrich dan@coneharvesters.com 2017-02-23T20:47:17+00:00 ecd1d020abdae3c3ce3643ddab3106501e62e7c0 Character set in POSIX is set by the locale defined (in decreasing order of precedence) by the LC_ALL, LC_CTYPE and LANG environment variables (I believe CHARSET is only historic). LC_ALL is cleared to ensure that LC_CTYPE takes effect, but LC_ALL is not used to set the locale to ensure that other parts of the locale aren't overriden, if set. Since there doesn't seem to be a cross-platform way of specifying a UTF-8 locale, and not all systems may support UTF-8, a <precheck> is used (where relevant) to skip the test if UTF-8 isn't in use. Test 1035 was also converted to UTF-8 for consistency, as the actual character set used there is irrelevant to the test. 
Character set in POSIX is set by the locale defined (in decreasing order
of precedence) by the LC_ALL, LC_CTYPE and LANG environment variables (I
believe CHARSET is only historic). LC_ALL is cleared to ensure that
LC_CTYPE takes effect, but LC_ALL is not used to set the locale to
ensure that other parts of the locale aren't overriden, if set.  Since
there doesn't seem to be a cross-platform way of specifying a UTF-8
locale, and not all systems may support UTF-8, a <precheck> is used
(where relevant) to skip the test if UTF-8 isn't in use.  Test 1035 was
also converted to UTF-8 for consistency, as the actual character set
used there is irrelevant to the test.
tests: Set CHARSET & LANG to UTF-8 in 1035, 2046 and 2047 2017-02-23T10:02:59+00:00 İsmail Dönmez ismail@i10z.com 2017-02-23T09:24:42+00:00 2bfe55037fe8beeecc573e27cb52c371d135bc0b Closes #1283 Fixes #1277 
Closes #1283
Fixes #1277
connection reuse: IDN host names fixed 2016-01-07T23:19:46+00:00 Michael Kaufmann mail@michael-kaufmann.ch 2016-01-07T17:00:00+00:00 d9b4d1ce20e89a00dba8afc3767845fb7e357b21 Use the ACE form of IDN hostnames as key in the connection cache. Add new tests. Closes #592 
Use the ACE form of IDN hostnames as key in the connection cache.  Add
new tests.

Closes #592