Comments on: HTTP compression filter on servlets : good idea, wrong layer

By: Adrian

Adrian — Sat, 23 Jan 2010 07:53:39 +0000

Hi Peter, and thanks for reading my old dusty blog. The article was written in 2005, and indeed some things are to be taken with a grain of salt. I second what you said, modern servlet-based architectures have solved the problem in a better way.

However, note that the Apache solution is still doable if needed.

By: Peter

Peter — Sat, 23 Jan 2010 07:05:26 +0000

The article is a bit misleading, as there is one flaw, you are making the assumption that the container is reverse proxying with an Apache front, a standalone servlet for instance cannot leverage those modules.

Fewer and fewer servlets are being configured this way, as more specialized and improved containers emerge, so no don’t agree with this article entirely despite some good tips nonetheless.

By: Netuality » SEO eye for the Tapestry guy

Netuality » SEO eye for the Tapestry guy — Sun, 21 Oct 2007 14:47:21 +0000

[...] with mod_rewrite in Apache. I do use Apache as a proxy server, in order to perform transparent and efficient gzip-ing on the fly…. Now, I only had to add the mod_rewrite filter and I’m ready to [...]