Hi Constantin, A couple of questions: 1. Why do you remove the etag? Our web server does gzip for static files, and in that case provides a different etag than the non zipped file. So far I did not see any problem with using the web server directly or behind squid. 2. When using this adapter with squid, does it gzip the file once before it gets into the cache, and then server it as binary directly from the cache without processing on every request, or does it gzip it on every request? If you gzip it once then squid needs to store at least two versions of the file, but it should do that anyway with vary header. More disk, less work for the CPU (a trade of that I found works well for our squid). Thanks, Elli ----- Original Message ----- From: Constantin Rack Sent: Sat, 4 Jul 2009 14:09:32 -0700 (PDT) Subject: VIGOS eCAP GZIP Adapter 1.1 released Dear all, we have just released an update of our GZIP eCAP adapter for Squid: http://www.vigos.de/products/eCAP/ ChangeLog: * FIX: Do not compress if response has a Content-Encoding header. * FIX: Do not compress if response has a Content-Range header. * FIX: Respect "Cache-Control: no-transform" header * FIX: Add warning header according to RFC 2616 * FIX: Remove ETag header on compressed response * FIX: Remove Content-Location header on compressed response Best Regards, Constantin -- VIGOS AG - High Performance Internet Technologies Steubenstrasse 26a, 58097 Hagen, Germany Telefon +49-2331-808189-25, Fax: +49-2331-808189-10 CEO: Constantin Rack, HR: AG Hagen HRB 4021 http://www.vigos.com/
