proxy + compress ?

hello everyone,

I have  lighttpd 1.4.18-1, running on Linux RHEL4 (with
updates from centos4). I set it up to run as a proxy for a
Zope app which runs on port 8080. It works ok via port 80
and 443 - thanks for making it so easy!

Now, the zope app doesn't compress it's content. I would
like lighty to do it for me. So I enabled the compress
module, configured it..and nothing changes. I changed the
order the module are defined in the config file, hoping that
would affect the order in which they are loaded/ executed,
no luck.

My relevant bits of configs are :

-----------------------------------
server.modules              = (
                                "mod_redirect",
                                "mod_access",
                                "mod_compress",
                                "mod_proxy",
                                "mod_accesslog" )

## change uid to <uid> (default: don't care)
server.username            = "lighttpd"

## change uid to <uid> (default: don't care)
server.groupname           = "lighttpd"

#### compress module
compress.cache-dir         =
"/var/cache/lighttpd/compress/"
compress.filetype          = ("text/plain",
"text/html")

proxy.debug=0
proxy.server = ( "" => 
                        ( ( 
                        "host" =>
"127.0.0.1",
                         "port" => 8080
                        ) )
                )
----------------------------

[rootnms lighttpd]# ls -l /var/cache/
drwxr-xr-x   3 root root 4096 Dec 10 12:56 lighttpd

[rootnms lighttpd]# ls -l /var/cache/lighttpd/
drwxr-xr-x  2 lighttpd lighttpd 4096 Dec 10 12:56 compress

the compress directory is also empty.

What am I missing? 

thanks in advance!
Beto
_________________________
{Beto|Norberto|Numard} Meijome

If you find a solution and become attached to it, the
solution may become your next problem.

I speak for myself, not my employer. Contents may be hot.
Slippery when wet. Reading disclaimers makes you go blind.
Writing them is worse. You have been Warned.

Am Dienstag, den 11.12.2007, 01:19 +1100 schrieb Norberto
Meijome:
> hello everyone,
> 
> I have  lighttpd 1.4.18-1, running on Linux RHEL4 (with
updates from centos4). I set it up to run as a proxy for a
Zope app which runs on port 8080. It works ok via port 80
and 443 - thanks for making it so easy!
> 
> Now, the zope app doesn't compress it's content. I
would like lighty to do it for me. So I enabled the compress
module, configured it..and nothing changes. I changed the
order the module are defined in the config file, hoping that
would affect the order in which they are loaded/ executed,
no luck.
> 

AFAIK mod_compress won't compress dynamic or proxied
content.
mod_deflate does.

http:/
/trac.lighttpd.net/trac/wiki/Mod_Deflate

--Regards
  Volker Schäfer

On Mon, 10 Dec 2007 16:03:43 +0100
Volker Schäfer <vsneopoly.de> wrote:

> AFAIK mod_compress won't compress dynamic or proxied
content.
> mod_deflate does.
> 
> http:/
/trac.lighttpd.net/trac/wiki/Mod_Deflate

gotcha, thanks 

so what does compress actually do ?

cheers,
B
_________________________
{Beto|Norberto|Numard} Meijome

Your reasoning is excellent -- it's only your basic
assumptions that are wrong.

I speak for myself, not my employer. Contents may be hot.
Slippery when wet. Reading disclaimers makes you go blind.
Writing them is worse. You have been Warned.