On Tue, 4 Feb 2014, Tatsuhiro Tsujikawa wrote:
Yes, twitter sends content-encoding: gzip. One possible solution is we pretend "" is specified in data->set.str[STRING_ENCODING] when we switched to HTTP2.
Exactly! Or perhaps to be more strictly only allowing gzip (as that's what http2-draft-09 says[1]), we set it to "gzip".
CURLOPT_ACCEPT_ENCODING should be ignored when http2 has been negotiated. [1] = http://tools.ietf.org/html/draft-ietf-httpbis-http2-09#section-9.3 -- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
