Sorry, making some corrections in this block:
El vie, 12 feb 2021 a las 13:32, Adrián Gimeno Balaguer
() escribió:
> Right. However, the key fact that has recently confirmed it's
> correctly working against it is that, while initially I thought their
> response was the same independently of the AC
Hi Ray,
> Please do not top-post it makes the conversation hard to follow. [1]
Ok. Thanks for correcting me.
> It looks like you have solved the first problem and your build is able to
> decode compressed content.
Right. However, the key fact that has recently confirmed it's
correctly working
drián
*De: *Ray Satiro via curl-library <mailto:curl-library@cool.haxx.se>
*Enviado: *viernes, 5 de febrero de 2021 21:52
*Para: *curl-library@cool.haxx.se <mailto:curl-library@cool.haxx.se>
*CC: *Ray Satiro <mailto:raysat...@yahoo.com>
*Asunto: *Re: CURLOPT_ACCEPT_ENCODIN
make any sense at all. I haven’t yet tried to analyze the network packets to determine the right data nature. Thanks for any response in advance. Regards,Adrián De: Ray Satiro via curl-libraryEnviado: viernes, 5 de febrero de 2021 21:52Para: curl-library@cool.haxx.seCC: Ray SatiroAsunto: Re: CURLOPT_ACCE
On 2/4/2021 10:07 AM, Adrián Gimeno Balaguer via curl-library wrote:
I’m using a self built libcurl shared library for embedded use in a
C++ application. In the attempt of requesting it to automatically
decompress response data from a remote server of interest by using a
line like the followi
