Hi, On Thu, Apr 28, 2016 at 6:13 AM, Ray Satiro via curl-library < [email protected]> wrote:
> I've noticed twitter is sending http2 gzip responses even though I'm not > using --compressed. I haven't encountered any other business that does > that. Is that allowed by the RFC? I searched it for gzip but it's not > mentioned once, and the compression sections seem to apply mostly to > headers. Web search only shows [1]. > > As far as I know early HTTP/2 draft allowed implicit "accept: gzip". This is a legacy of SPDY. RFC 7540 does not allow this, and we have to follow what RFC 723x say. Best regards, Tatsuhiro Tsujikawa > curl -v https://twitter.com | gzip -d > > curl 7.49.0-DEV (i686-w64-mingw32) libcurl/7.49.0-DEV mbedTLS/2.2.1 > zlib/1.2.8 libidn/1.32 libssh2/1.7.0 nghttp2/1.9.2 > Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 > pop3s rtsp scp sftp smtp smtps telnet tftp > Features: AsynchDNS Debug TrackMemory IDN IPv6 Largefile SSPI Kerberos > SPNEGO NTLM SSL libz HTTP2 > > > [1]: https://github.com/golang/go/issues/13298 > > > > ------------------------------------------------------------------- > List admin: https://cool.haxx.se/list/listinfo/curl-library > Etiquette: https://curl.haxx.se/mail/etiquette.html
------------------------------------------------------------------- List admin: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
