I am not 100% sure. It is better to check it I think it is configurable but
I am
not sure what is the default behavior.
On Thu, Sep 15, 2011 at 9:52 PM, Thomas Weholt wrote:
> Aha! That's briliant, but doesn't nginx set those headers for me when
> returning a static resource like a image?
>
> Tho
Aha! That's briliant, but doesn't nginx set those headers for me when
returning a static resource like a image?
Thomas
On Thu, Sep 15, 2011 at 4:52 PM, Ilian Iliev wrote:
> How about to set correct headers and make the images cached on user side
> instead
> of wasting memchached resources?
> If
How about to set correct headers and make the images cached on user side
instead
of wasting memchached resources?
If you are serving tons of thumbs multiple times I bet that the traffic will
be bigger problem
than the time it took for these images to be read from disk.
Check this post ->
http://il
What is your goal in doing this? You are unlikely to see any
performance gains from this effort.
It won't render any faster for your users. Sending bytes over the
network is far slower than reading them off disk, so it's not likely to
be a bottleneck in terms of page loading.
Your filesystem
Good point Cliff! I just assumed serving static content would benefit
from caching, but perhaps my effort is more well spent focusing on
other aspects of my app right now.
Thanks :-)
Thomas
On Thu, Sep 15, 2011 at 3:42 PM, J. Cliff Dyer wrote:
> What is your goal in doing this? You are unlike
5 matches
Mail list logo
