String instance is broken with non-ASCII data

Although the package works with String, and indeed encourages its use by having that be the default type in some of the API helper functions, the handling of non-ASCII data is completely broken. We should be doing encoding properly to be consistent with the Content-Type header, both when sending and receiving.

This has been reported by a couple of users so far and is clearly pretty nasty, but I don't think it's trivial to fix because presumably the receiving and sending sides can use different encodings and when sending requests we ought to be optionally giving the user control of the encoding.

The alternative of removing the String instances completely is likely to be very disruptive so I don't think it's a reasonable option.

Empieza rastreando las rutas auxiliares de la API de String para enviar y recibir datos; después, inspecciona cómo cada ruta gestiona la cabecera Content-Type y la codificación de caracteres. Compara la codificación utilizada en ambos lados e identifica dónde podrían controlarla los llamadores; se considera terminado cuando los datos String no ASCII se gestionan de forma coherente al enviar y recibir, sin eliminar instancias de String.

Escrito por el modelo de indexación a partir del texto del issue.