Thanks,<br><br>That helps me understand how hash tables work.<br><br>Question: Is this for proxy_cache:<br>Bugfix: now nginx takes into account the "X-Accel-Expires", "Expires", and "Cache-Control" header lines in a backend response.<br>
<br>Or are files always cached for time specified in proxy_cache_valid?<br><br>Purging would be amazing, that way I could set proxy_cache_valid to a day or more, and know that if a change was made I could just issue a purge for that specific key, or key path.<br>
<br>Any plans for nginx to manage the cache by doing a HEAD request looking for changed content automatically on the origin at certain intervals?<br><br>Thanks!<br><br>John<br><br><br><br><br><br><br><div class="gmail_quote">
2009/4/10 Igor Sysoev <span dir="ltr"><<a href="mailto:is@rambler-co.ru">is@rambler-co.ru</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thu, Apr 09, 2009 at 02:27:15PM -0500, Resicow wrote:<br>
<br>
> Hi Igor (and everyone else),<br>
><br>
> I had a few quick questions about the new proxy_cache feature, and I<br>
> apologize if they have already been answered.<br>
><br>
> 1) What about query_strings? Does proxy_cache ignore or include<br>
> query_strings? Is there a way to have it ignore query_strings in the URL?<br>
<br>
</div>By default qeury strings are included. You may ignore them using something<br>
like this:<br>
<br>
proxy_cache_key $host/$uri";<br>
<br>
The default proxy_cache_key approximates<br>
<br>
proxy_cache_key $scheme$proxy_host$uri$is_args$args;<br>
<div class="im"><br>
> 2) How scalable is this system? Could it handle 50 million different<br>
> URIs for instance?<br>
<br>
</div>Each key takes 128 bytes in shared memory zone. Therefore you need 6.1G zone:<br>
<br>
key_zone=NAME:6200m;<br>
<div class="im"><br>
> 3) Any plans for purge capabilities somehow, in the event you need the<br>
> content flushed right away?<br>
<br>
</div>Yes, there are such plans.<br>
<div class="im"><br>
> Keep up the great work, thanks for making the world's best server!<br>
><br>
> Thanks,<br>
><br>
> John<br>
><br>
><br>
><br>
><br>
><br>
> Igor Sysoev wrote:<br>
> >On Wed, Apr 08, 2009 at 11:16:30AM +0000, Glen Lumanau wrote:<br>
> ><br>
> ><br>
> >>How about jpg, css, js or any other files?<br>
> >><br>
> ><br>
> >No problems with these files. Actually, there are no problems with flv<br>
> >itself. The issue is when you want to get /some.flv?start=5000.<br>
> >However, it seems flv handler can be converted easy enough to filter.<br>
> ><br>
> ><br>
> >>------Original Message------<br>
> >>From: Igor Sysoev<br>
> >>Sender: <a href="mailto:owner-nginx@sysoev.ru">owner-nginx@sysoev.ru</a><br>
> >>To: <a href="mailto:nginx@sysoev.ru">nginx@sysoev.ru</a><br>
> >>ReplyTo: <a href="mailto:nginx@sysoev.ru">nginx@sysoev.ru</a><br>
> >>Subject: Re: Re: nginx + caching of static files<br>
> >>Sent: Apr 8, 2009 6:04 PM<br>
> >><br>
> >>On Wed, Apr 08, 2009 at 10:51:59AM +0800, ???? wrote:<br>
> >><br>
> >><br>
> >>>Dear Igor,<br>
> >>><br>
> >>>Then, how to use proxy_cache WITH flv streaming?<br>
> >>>I tried proxy_cache feature, but it seems that the flv streaming<br>
> >>>function does not work with proxy_cache.<br>
> >>><br>
> >>No, flv is not filter, but handler, thefore it's not possible.<br>
> >><br>
> ><br>
> ><br>
> ><br>
><br>
<br>
</div><div><div></div><div class="h5">--<br>
Igor Sysoev<br>
<a href="http://sysoev.ru/en/" target="_blank">http://sysoev.ru/en/</a><br>
<br>
</div></div></blockquote></div><br>