So this has to do with the way caching works in Chrome. I don’t have personal experience with Chrome’s codebase, but I do know a bit about the theory of it. (I also found a reference to Chrome’s cache implementation here for the more curious: chromium disk cache) For reference, here is a screenshot of … Read more
See this answer: Difference between three .htaccess expire rules If a response includes both an Expires header and a max-age directive, the max-age directive overrides the Expires header, even if the Expires header is more restrictive. This rule allows an origin server to provide, for a given response, a longer expiration time to an HTTP/1.1 … Read more
WebAPI does not have any built in support for the [OutputCache] attribute. Take a look at this article to see how you could implement this feature yourself.
As suggested in the comments, you can create an ActionFilterAttribute. Here’s a simple one that only handles the MaxAge property: public class CacheControlAttribute : System.Web.Http.Filters.ActionFilterAttribute { public int MaxAge { get; set; } public CacheControlAttribute() { MaxAge = 3600; } public override void OnActionExecuted(HttpActionExecutedContext context) { if (context.Response != null) context.Response.Headers.CacheControl = new CacheControlHeaderValue() { … Read more
Unfortunately, caching is not built into ASP.NET Web API. Check this out to get you on track: http://www.strathweb.com/2012/05/output-caching-in-asp-net-web-api/ An updated resource here: https://github.com/filipw/AspNetWebApi-OutputCache EDIT: As of 2020-02-03, even though this answer is quite old, it’s still valid. Both of the URL’s above lead to the same project, ASP.NET Web API CacheOutput by Filip W
See the below flow chart for better understanding Ref: (https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching?hl=en#cache-control)
For Angular 2 and newer, the easiest way to add no-cache headers by overriding RequestOptions: import { Injectable } from ‘@angular/core’; import { BaseRequestOptions, Headers } from ‘@angular/http’; @Injectable() export class CustomRequestOptions extends BaseRequestOptions { headers = new Headers({ ‘Cache-Control’: ‘no-cache’, ‘Pragma’: ‘no-cache’, ‘Expires’: ‘Sat, 01 Jan 2000 00:00:00 GMT’ }); } Module: @NgModule({ … … Read more
I have faced same problem. I had to supply ‘public’ headers my cdn. By default when gateway caching is enabled in prod mode, it returns 200 OK with private, nocache must validate headers. I solved problem this way. In app.php, before I send response to user ($respond->send), I have overwritten the cache control header to … Read more
The corresponding RFC 2616 in section 9.5 (POST) allows the caching of the response to a POST message, if you use the appropriate headers. Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields. However, the 303 (See Other) response can be used to direct the user agent … Read more