no-cache

For some reason Laravel seems to be manipulating the response headers 'Cache-Control' on the very last moment. I want to make browser caching possible. class TestController extends Controller { public function getTest() { $response = new \Illuminate\Http\Response('test', 200, array( 'Cache-Control' => 'max-age='.(config('imagecache.lifetime')*60).', public', 'Content-Length' => strlen('test'), )); $response->setLastModified(new \DateTime('now')); $response->setExpires(\Carbon\Carbon::now()->addMinutes(config('imagecache.lifetime'))); return $response; } } Even when I use a 'after-middleware'

How can I set the response header for each call in my application made with Spring Boot? I would like to try to use a filter to intercept all the calls and be able to set the response header. I followed the guide Disable browser caching HTML5 , but only set the request header, and not always. There are three ways to do this: Set the response for a specific controller, in the Controller class: @Controller @RequestMapping(value = DEFAULT_ADMIN_URL + "/xxx/") public class XxxController .... @ModelAttribute public void setResponseHeader(HttpServletResponse response) { response.setHeader("Cache

This is a follow up question to Using 301/303/307 redirects for dynamic short urls , where I try to determine the best method for implementing short url redirection when the destination url will change on a frequent basis. While it seems that 301 and 307 redirects both perform the same way, the issue that concerns me is 301 redirect caching (as documented here )- is the best way to avoid this to use 307 redirects instead (I'm assuming 307 redirects will never cache?), or to explicitly send a no-cache header ("Cache-Control: no-cache, must-revalidate")? Don't try to avoid 301 caching. If you

We have been having a problem with Chrome caching a resource on our Glassfish server. The expires and no-cache headers are not being sent and the resource (an approximately 4 MB SWF file) is being cached by Chrome -- despite the presence of the Last-Modified header. Sometimes Chrome will get a 304 code, and other times it simply does a 200 (from cache). I understand the 304 -- Chrome is likely checking the most recent Last-Modified date with the cached version to decide. But other times it does the 200 (from cache), which does not return any header information and appears that Chrome is simply

I'm writing a client that is making repeated http requests for xml data that is changing over time. It looks like the Android stack is caching my page requests and returning the same page repeatedly. How do I make sure it gets a fresh page each time? -- code --- HttpClient client = new DefaultHttpClient(); HttpGet request = new HttpGet(url); HttpResponse response; response = client.execute(request); InputStream in; in = response.getEntity().getContent(); BufferedReader reader = new BufferedReader(new InputStreamReader(in)); Thanks, Gerry Kylar add a HTTP header: Cache-Control: no-cache and see

I'm told to prevent user-info leaking, only "no-cache" in response is not enough. "no-store" is also necessary. Cache-Control: no-cache, no-store After reading this spec http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html , I'm still not quite sure why. My current understanding is that it is just for intermediate cache server. Even if "no-cache" is in response, intermediate cache server can still save the content to non-volatile storage. The intermediate cache server will decide whether using the saved content for following request. However, if "no-store" is in the response, the