4 messages in ru.sysoev.nginxgzip+cache-dir: What's the easiest wa...
FromSent OnAttachments
Sven C. KoehlerSep 24, 2008 2:21 pm 
mikeSep 24, 2008 2:45 pm 
Sven C. KoehlerSep 24, 2008 3:27 pm 
mikeSep 24, 2008 3:37 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:gzip+cache-dir: What's the easiest way to port this lighty config excerpt?Actions...
From:Sven C. Koehler (schw@snafu.de)
Date:Sep 24, 2008 2:21:57 pm
List:ru.sysoev.nginx

Hi,

I am wondering what might be the easiest way to resemble the semantics of lighttpd's compress.cache-dir:

| server.modules = ( "mod_compress" ) | compress.filetype = ("text/javascript", "text/css") | server.document-root = "/web" | $HTTP["url"] =~ "^/static/" { | compress.cache-dir = "/web_cache" | }

What it does is to automatically generate gzipped representations of files below /web/static/ (according to their last-modified time) in the directory /web_cache. I find this very handy and it greatly reduces the load for serving compressed files which change rarely.

On nginx, however, I cannot see how I could resemble this semantic with only "gzip on" or "gzip_static on"--is that correct?

Best,

Sven