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.
RE: Does curl do anything special with non-ASCII characters in HTTP header values?
From: Daniel Stenberg via curl-users <curl-users_at_cool.haxx.se>
Date: Sat, 19 Sep 2020 23:35:36 +0200 (CEST)
Date: Sat, 19 Sep 2020 23:35:36 +0200 (CEST)
On Sat, 19 Sep 2020, Steve Perkins via curl-users wrote:
> At any rate, I will probably refactor this application, to not rely on HTTP
> header values for potentially non-ASCII strings. Even if I could get it to
> work via manual conversion from "ISO 8859/1" on the server, that feels like
> an awfully brittle solution. I would love to better understand the strange
> behavior that I'm seeing, but I am satisfied now that curl isn't doing
> anything "magical" that I can emulate.
The reason for this "non-treatment" in curl is that HTTP headers have no
defined behavior for non-ascii strings. There's no defined way to encode
charsets in generic HTTP headers.
--
/ daniel.haxx.se | Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-09-19