Welcome! Log In Create A New Profile

Advanced

Re: Strange problem with cache

October 26, 2012 07:57AM
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

I use django in my project and its static/collectstatic process. So, i force the mtime of each static file collected, afet each collecstatic operation. I give the command line if someone fall in the same trap:
./manage.py collectstatic --noinput && find static -type f -exec touch -t $(date +%m%d%H)00 '{}' \;

Now, the cache is working as intended and my servers are in active-active setup.

Thanks for your answer that leads me to the solution
Subject Author Posted

Strange problem with cache

florian.iragne October 25, 2012 04:34PM

Re: Strange problem with cache

Maxim Dounin October 26, 2012 06:42AM

Re: Strange problem with cache

florian.iragne October 26, 2012 07:57AM

Re: Strange problem with cache

Oleksandr V. Typlyns'kyi October 27, 2012 08:38AM

Re: Strange problem with cache

florian.iragne October 29, 2012 03:59AM

Re: Strange problem with cache

Maxim Dounin October 29, 2012 04:40AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 60
Record Number of Users: 5 on July 11, 2016
Record Number of Guests: 271 on July 19, 2016
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready