On 31/12/2020 16:52, Tomalak Geret'kal wrote: > Per the headers, it's gzip-encoded. If you output to > out.html.gzip, then unzip, it'll be fine. > > I don't know why this just happened. I would have thought > curl would auto decode the contents to be honest. > > curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 > NSS/3.53.1 zlib/1.2.7 libidn/1.28 libssh2/1.8.0 > Protocols: dict file ftp ftps gopher http https imap imaps > ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp > Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM > NTLM_WB SSL libz unix-sockets > > Tom > By the way, passing --compressed will request a gzip encoded response then also decompress the result automatically.
Perhaps there's a bug with curl not decoding regardless (based on response headers), and/or perhaps Amazon only just started gzip-encoding the response regardless of the request headers. Cheers ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
