There is a weird behavior regarding output caching in an ASP.NET 4 application on IIS 7.5. I was able to repeat the problem simply on other empty settings, I am sure that this is a mistake, but I do not know how to report it to Microsoft.
A site in IIS responds to more than 1 domain, the .NET application checks the host name and accordingly creates the content. For example, it may print the name of the request URL on a blank page. For example, www.first-domain.com and www.second-domain.com
Web.config has corresponding caching, urlCompression and httpCompression, which are disabled under the system .webServer node.
The aspx page sets the cache management header for the public, either with an expiration date or with a maximum value.
A visit to www.first-domain.com displays a page that successfully records "www.first-domain.com".
However, a visit to www.second-domain.com brings up a page that writes "www.first-domain.com".
While examining traces of failed requests, System.Web.Caching.OutputCacheModule detected cached output (even if the .config files disabled this function), the cache matched even if the hostname of the URL is different, and thus the second request will output the results of the first request to another domain until the maximum age / expiration date is set, until the correct page for the second domain appears.
- , OutputCache web.config, , , , , , , .
MSDN , OutputCacheModule.
- , URL- URL- ( IIS).
.
Update:
SetSlidingExpiration , - . - , , - , , , .