Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
String encoding used by CURLOPT_ERRORBUFFER
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Andreas Falkenhahn via curl-library <curl-library_at_cool.haxx.se>
Date: Thu, 14 Jan 2021 19:46:33 +0100
Is there any specification concerning the encoding used by the string copied to CURLOPT_ERRORBUFFER in case of an error?
On my German Windows system I often seem to be getting ISO 8859-1. For example, the error message for CURLE_SSL_CONNECT_ERROR is this:
"schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - Die Sperrfunktion konnte die Sperrung nicht überprüfen, da der Sperrserver offline war."
Note the German umlauts "ü" in the error message.
Is there any way to make curl return something more i18n-proof, e.g. UTF-8? If not, consider this a feature request ;)
Date: Thu, 14 Jan 2021 19:46:33 +0100
Is there any specification concerning the encoding used by the string copied to CURLOPT_ERRORBUFFER in case of an error?
On my German Windows system I often seem to be getting ISO 8859-1. For example, the error message for CURLE_SSL_CONNECT_ERROR is this:
"schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - Die Sperrfunktion konnte die Sperrung nicht überprüfen, da der Sperrserver offline war."
Note the German umlauts "ü" in the error message.
Is there any way to make curl return something more i18n-proof, e.g. UTF-8? If not, consider this a feature request ;)
-- Best regards, Andreas Falkenhahn mailto:andreas_at_falkenhahn.com ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2021-01-14