[web2py] Fwd: client side caching

But why do you think that it should be 304? https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304 -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) ---

[web2py] Fwd: client side caching

Oh, sorry, it is about server side cache -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Googl

[web2py] Fwd: client side caching

https://py4web.com/_documentation/static/index.html#chapter-04 See at the end -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message b

[web2py] Fwd: client side caching

Excuse me for the crossposting, maybe someone else in here can answer my question... I haven't found nothing ready to use out of the box in py4web for caching controller results client side so I thought to implement my self following the cache.action decorator code in web2py, but without succe