Suzanne Capener wrote: > 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?
Never tried this together with CF. But with static content, it does exactly what it is supposed to do. > Are there any repercussions from enabling this such as performance loss? Not from the process of adding the headers. But you might see a lot more requests, depending on how far in the future you set the expiracy date. If you do this to ensure immediate expiry, I would recommend *not* doing so for image directories. Jochem ______________________________________________________________________ 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
