search for: all_post

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm:

I am using memcache for caching in my rails app and currently I have a dev and a production environment. I would like to run the dev environment without caching so that I can debug more easily but I wanna enable the caching in production obviously. I am using github and capistrano for deployment. Without doing a check at every statement where I can potentially dig into the cache, is there any

...fy max age for regular content, I do have expires-max set for css, jpg etc. here is my nginx.conf file.. http://pastie.org/1167080 So why is this cache-control is being set? How can I control this cache-control, because the side effect of this is kinda bad. This is what happens. 1 - User request all_posts listing and get a list of 10 pages (paginated) 2 - User view page 1, 2 3 and the respective caches are created. 3 - User goes back to page 1 and firefox does not even make a request to the server. Normally I would expect it would reqeust and hit the cache created in step #2. The other issue is...