On Feb 4, 2014, at 6:09 AM, Daniel Stenberg <[email protected]> wrote:
> I also made libcurl now gzip decode automatically for http2.

This was almost correct, the thing is that non-compressed responses are still 
allowed and for example https://106.186.112.116/ sends such responses and was 
thus broken. I attached a patch that fixes this, by relying on the response 
header for content encoding.

Regards,
Fabian

Attachment: 0001-http2-rely-on-content-encoding-header.patch
Description: Binary data

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Reply via email to