I have added the first part of gzip support to varnish-trunk. This is new code with semi-twisted logic under the hood, so I am very dependent on you guys helping to test it out.
If you set the paramter http_gzip_support to true, varnish will always send "Accept-encoding: gzip" to the backend. If the client does not understand gzip, varnish will gunzip the object during delivery. This means that you only will only cache the gzip'ed version of objects. The responsibility for gzip'ing the object is with your backend, Varnish doesnt don't know which objects you want to gzip and which not (ie: images: no, html: yes, but what about .cgi ?) ESI is not supported with gzip mode yet, that is the next and even more involved step. When you file tickets, please use "version = trunk" in trac Thanks in advance, Poul-Henning PS: Also be aware that "purge" is now called "ban" in -trunk. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-misc mailing list [email protected] http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
