Sorry that it's completely different of what you expect but I offer to
not use it at all in this case.

My workaround is to send Expires header and Cache-Control: max-age.
IMO this is good enough without making complicated work to answer with
"last modified".

Or send real "old one" like Facebook does:
http://redbot.org/?uri=http%3A%2F%2Fstatic.ak.fbcdn.net%2Frsrc.php%
2FzEX21%2Fhash%2F75j4m1ms.png

There is no good in sending "actual" last modified timestamp to client.
It was designed to make intellectual caching but only makes things
confusing.

Alex.




On Wed, 2010-09-29 at 11:22 -0700, Fima Leshinsky wrote:
> Is there a way to get nginx to send a last-modified of the "master"
> object when SSI is enabled outside of the: add_header Last-Modified
> "blah" directive? Open to any and all work arounds.
>
>
> Thanks in advance.
>
>
> Fima
>
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx



_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx