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
The <meta http-equiv> tags are only used when the HTML file in question is been opened from a non-HTTP resource such as local disk file system (via file:// URI) and not when the HTML file in question is been opened from a real HTTP resource (via http:// URI). Instead, the real HTTP response headers as … Read more
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
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