> IIS allows you to configure settings that will ensure that > content automatically expires at any point in time by using > the HTTP Headers property sheet. When content expiration is > enabled, the Web browser compares the current date to the > expiration date to determine whether to display a cached page > or request an updated page from the server. > > Has anyone used this and has it been successfull? > Are there any repercussions from enabling this such as > performance loss?
For CF pages, you'd typically do this stuff in your code, with the appropriate CFHEADER and CFCACHE tags. I don't think that IIS's settings will work for CF pages, just for static pages. In any case, even if it did technically work, the conditions in which you'd want a static page to be pulled from the client's cache would most likely be different than those for a dynamically generated CF page. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
