Posted - October 24 2012 : 15:47:26
| Here's something which people might find useful....
We found today that in some instances (eg when generating lots of static pages in one go), browsing a url of a changed asp file still executed an old version of the asp file, not the version that was actually on the site.
Turns out that it's a hosting/server issue to do with file-cacheing on iis6:
IIS 6.0: Delay in Serving Updated Active Server Pages:
I've got no idea if this is potentially an issue for other hosts (such as vpasp; this issue was found on a non-vpasp-hosted server), but hopefully this'll help people if they have a situation where they browse an asp file on their site and it simply doesn't show the correct/latest version of that asp file, especially when it comes to static generated asp pages.
I guess it's quite rare that you'd get these symptoms because it's asp-code that it's cacheing rather than html code (so the data is dynamic/new even though the asp file being executed is old), it only really becomes an issue if the page that you generated now points to a different product/category/content-record than before (which is what happened in our situation; a static file turned from a products-list to a sub-category list page, but we couldn't see the change as the products-list version was cached on the server)
Follow us on Twitter: http://twitter.com/bigyellowzone
Web Design, Online Marketing and VPASP addons