Re: [web2py] changing client side caching headers expires or cache-control value

2013-10-16 Thread molhokwai
Cleared the cache to be sure and retried... Getting '304 Not Modified' status code for local static items to be cached But '200 (from cache)' for remote items... So seems like this has to do with localhost requesting local resources... Client side caching works perfectly online, so not an issue, b

Re: [web2py] changing client side caching headers expires or cache-control value

2013-10-16 Thread Dave S
On Wednesday, October 16, 2013 11:06:23 AM UTC-7, molhokwai wrote: > > Well... > It doesn't seem to work on local dev_appserver, but it actually works, > when deployed on appspot.com... > So, anyway, problem solved... > > Different IP or domain name? If your browser's cache wasn't cleared, the

Re: [web2py] changing client side caching headers expires or cache-control value

2013-10-16 Thread molhokwai
Well... It doesn't seem to work on local dev_appserver, but it actually works, when deployed on appspot.com... So, anyway, problem solved... Thanks On Wed, Oct 16, 2013 at 4:14 PM, molhokwai wrote: > Hi, > > I've tried changing client side caching headers expires or cache-control > value (fr