ASP.NET HTTPS/SSL Caching and Dynamic Pages

Question

I have an IIS6 ASP.NET 2/3.5 site that ALWAYS seems to be caching anything that goes through a https request. HTTP requests always work the same, but i see old/invalid data on https requests.

I see this a lot with pages where i'm doing http rewriting--but in general, it almost seems like the site has one set of values it shows to http requests and another to https requests-- without having any backend code that renders differently based upon the scheme.

Any ideas? Does IIS have a weird ssl caching option i'm not aware of?

Answer 1

在IIS中，端口设置错误-尽管域是正确的，因为我使用的是端口443，所以将其转发到另一个站点（因为设置了主机头）。