You can cache the image filter using either lua or through a proxy pass to yourself.<br><br>But yes I agree with your points.<br><br><div class="gmail_quote">On Fri, May 27, 2011 at 10:28 AM, adamchal <span dir="ltr"><<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I've been following this discussion and I'm anxiously waiting for some<br>
resolution. I think Maxim's approach is right: implementing a<br>
gzip_cache filter that could be used for caching any content. This<br>
would allow for much more flexibility than just using it for<br>
proxy_pass/proxy_cache.<br>
<br>
This could effectively eliminate the gzip_static filter. If you have<br>
plain HTML served and "gzip on;" plus something like "gzip_cache on;"<br>
all of your plain text content would be served using the cached gzip<br>
content. Similarly, you would be able to use this for proxy_pass,<br>
proxy_store, fastcgi_pass, etc. It wouldn't matter since the caching of<br>
the gzip'd content would be stored in the gzip_cache filter and<br>
negotiated directly with the client.<br>
<br>
There's a lot of chatter about using Varnish or Lighty or <insert<br>
another web/cache server here> to give Nginx pre-gzipped data in a proxy<br>
response. This sounds absolutely horrible. The bottom line is that if<br>
Nginx is the webserver that is dealing with the client directly, it<br>
should then be Nginx's responsibility to serve the appropriate version<br>
(gzip'd or plain text) content based on the client's request headers.<br>
That being said, Nginx should be managing it's own cache of filtered<br>
items.<br>
<br>
The same goes for the image_filter. Currently, I use the image_filter<br>
for a project and I'm bummed out that Nginx is scaling the same image<br>
over and over each time it is requested. An image_filter_cache would be<br>
another great feature.<br>
<br>
Am I on the right track?<br>
<br>
Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,120314,201370#msg-201370" target="_blank">http://forum.nginx.org/read.php?2,120314,201370#msg-201370</a><br>
<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://thewarezscene.org" target="_blank">Warez Scene</a> <a href="http://www.nexusddl.com" target="_blank">Free Rapidshare Downloads</a><br><br>