On Jul 10, 2009, at 8:43 AM, Álvaro Justen [Turicas] wrote: > You can test setting HTTP header Pragma to 'no-cache' as W3C says[1] > or if you are suspecting that web2py is setting headers in a way you > don't want you could view headers (using Firefox addon Live HTTP > Headers, wget etc.) to make sure it's ok. An example:
I've been using curl -i (include headers) or -I (headers only). Here's the static css file: HTTP/1.1 200 OK Content-Length: 8861 Last-Modified: Sat, 04 Jul 2009 20:17:11 GMT Pragma: cache Cache-Control: private Content-Type: text/css Date: Thu, 09 Jul 2009 21:58:11 GMT Server: CherryPy/3.1.0beta3 WSGI Server Here's the dynamic one (a different file, though, and via Apache; the interesting part is the caching): HTTP/1.1 200 OK Date: Fri, 10 Jul 2009 16:02:50 GMT Expires: Fri, 10 Jul 2009 16:02:50 GMT Pragma: no-cache Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre- check=0 Content-Length: 84 Content-Type: text/css --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
