>>>>> "beebee" == beebee <[email protected]> writes:
Hi, beebee> You should probably be careful not to confuse content-encodeing beebee> and transmission-encoding. beebee> You will find much of this covered here: beebee> http://redmine.lighttpd.net/issues/2221 I had a look around, and it seems like most servers send Content-Encoding, and that's what most browsers expect: http://jython.xhaus.com/http-compression-in-python-and-jython/#encoding http://mail-archives.apache.org/mod_mbox/tomcat-dev/200109.mbox/%3cb7b9efc5.2d40%[email protected]%3e Lighttpd's mod_compress also uses Content-Encoding: http://redmine.lighttpd.net/projects/lighttpd/repository/entry/trunk/src/mod_compress.c beebee> The lighttpd strategy of keeping a cache of compressed files is beebee> interesting. In any case if there is support for sending gz beebee> compressed "if a pre-compressed file is available" it seems odd beebee> not to do the compression is if needed. While we could certainly do something like that, I don't we really need to. Busybox's goal is cleary to keep things as simple as possible, and doing a simple for i in `find /var/www -name \*.html' -o -name '*.css' -o -name '*.js'`; do gzip -c -9 < $i > $i.gz done Would work for most people. -- Bye, Peter Korsgaard _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
