On Tue, 10 Jul 2018, E T wrote:

> Content-Encoding: binary

Your requeset ask for some specific encodings and the server instead sends you
this made up content-encoding. libcurl doesn't know about any "binary"
encoding and bails out. This is a bad server.

A work-around for this particular site would be to disable content-encoding so
that libcurl won't try to decode it, but I realize it is hard to automate
based on such a vague error code as CURLE_WRITE_ERROR.

Any suggestions on what and how libcurl could do better here?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html