great!<br><br><div><span class="gmail_quote">On 7/17/07, <b class="gmail_sendername">Igor Sysoev</b> <<a href="mailto:is@rambler-co.ru">is@rambler-co.ru</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Jul 17, 2007 at 12:32:08PM +0200, Janko Hauser wrote:<br><br>> Am 17.07.2007 um 12:11 schrieb Igor Sysoev:<br>><br>> >Changes with nginx 0.6.4 17<br>> >Jul 2007
<br>> ><br>> > *) Security: the "msie_refresh" directive allowed XSS.<br>> ><br>> > *) Change: the "proxy_store" and "fastcgi_store" directives were<br>> > changed.
<br>> ><br>> > *) Feature: the "proxy_store_access" and "fastcgi_store_access"<br>> > directives.<br>><br>> First let me say many thanks for this great software. I think I'm not
<br>> alone, if I say, that nginx is the second most valuable component in<br>> our setup besides the application server itself in use (Zope in our<br>> case).<br>><br>> After the great value of the memcache-module I'm quite eager to learn
<br>> more about the caching possibilities introduced in this new release.<br>> Is there some more information how to use these new directives and<br>> what the general idea or concept stands behind them?<br><br>
proxy_store is not cache, it's rather mirror on demand:<br><br>location /images/ {<br> root /data/www;<br> error_page 404 = /fetch$uri;<br>}<br><br>location /fetch {<br> internal;<br>
<br> proxy_pass <a href="http://backend">http://backend</a>;<br> proxy_store on;<br> proxy_store_access user:rw group:rw all:r;<br> proxy_temp_path /data/temp;<br><br> alias /data/www;
<br>}<br><br>if file is not found, then it will be fetched from backend and stored<br>in 'root/alias' or in path specified explicitly:<br><br>proxy_store /data/www$original_uri;<br><br><br>--<br>Igor Sysoev<br><a href="http://sysoev.ru/en/">
http://sysoev.ru/en/</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>$B7/Ld]E4|L$M-4|!$GC;3Lk1+^}=)CS!#2?aD6&Qr@>cY?$!$RJOCGC;3Lk1+;~!#(B