Hello!

On Sat, Oct 27, 2012 at 03:35:51PM +0300, Oleksandr V. Typlyns'kyi wrote:

> Yesterday Oct 26, 2012 at 07:57 florian.iragne wrote:
>
> > Ok, now i understand. The browser sends a request withe the
> > if-not-modified-since corresponding to one server to the other server, and
> > this one reply with 200 since the mtime is in the future of the
> > if-not-modified-since
> >
> > is there any simple solution to handle this? I don't want to rsync assets
> > between the servers
>
> http://nginx.org/r/if_modified_since
> if_modified_since before;

1) This will work only if you'll switch off ETag's as well.

2) This isn't a solution, but a bandaid. It won't fix the real
problem (mtimes mismatch), but will make response with greatest
mtime eventually win. Even with only 2 servers used this
will still result in about 1.5x more 200 responses than needed.

--
Maxim Dounin
http://nginx.com/support.html

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