I'm not sure if this actually counts as a bug but currently [1] curl will
send the following Accept-Encoding header when using the --compress option

Accept-Encoding: deflate, gzip

I was wondering if the order could be reversed? Since IE and Firefox (at
least ) send "gzip, deflate" when they request pages and (it appears) the
defacto standard is for the server to serve up the first match.

This is mainly prompted by some testing I was doing to make sure I was not
using deflate anywhere due to the incompatibility between Microsoft's and
other people's implementation [2] .

[1] $ curl --version
curl 7.19.5 (i486-pc-linux-gnu) libcurl/7.19.5 OpenSSL/0.9.8g zlib/1.2.3.3
libidn/1.15
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

[2] http://www.subbu.org/blog/2008/03/ie7-deflate-or-not (see comments)

-- 
Simon Lyall  |  Very Busy  |  Web: http://www.darkmere.gen.nz/
"To stay awake all night adds a day to your life" - Stilgar | eMT.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html