We've had a DynamicWeb Server running in our test environment for quite sometime now. But we have a small issue with the configuration.
It Cache's imported files like images and stylesheets (both external css files and the DynamicWeb stylesheet), so whenever we make a change,
we have to either rename the file, or wait for the server to drop the Cached file, witch is quite annoying.
Have anyone here experienced anything similar or know how to fix this cache issue.
The server is a Windows Server 2003 (Standard edition R2) with IIS 6.0
Developer forum
E-mail notifications
Server Cache Problem
Posted on 12/03/2007 10:20:35
Replies
Posted on 14/03/2007 11:24:36
Hi,
I sometimes experience that problem! I found three solutions that help me quite a bit!
If you have a page that keeps caching and you don't want it to, just set up the page's cache to disabled (Edit the page's properties)
Another thing you can do is go to the File Manager, there's folder named "Cache" or "Cache.NET". Delete all it's contents
Last but not the least, on the URL add the variable refresh=yes. e.g www.yourdynamicwebsite.com/default.aspx?ID=1&refresh=yes
Good luck
// nuno
I sometimes experience that problem! I found three solutions that help me quite a bit!
If you have a page that keeps caching and you don't want it to, just set up the page's cache to disabled (Edit the page's properties)
Another thing you can do is go to the File Manager, there's folder named "Cache" or "Cache.NET". Delete all it's contents
Last but not the least, on the URL add the variable refresh=yes. e.g www.yourdynamicwebsite.com/default.aspx?ID=1&refresh=yes
Good luck
// nuno
Posted on 14/03/2007 13:05:16
Just a small point. refresh=yes refreshes the navigation structure in frontend, which is also cached, and can be used if new pages are not displayed in the menu. If you want to flush the cache for a single page, please use Purge=True, e.g.:
http://www.mysite.dk/Default.aspx?ID=10&Purge=True.
http://www.mysite.dk/Default.aspx?ID=10&Purge=True.
Posted on 14/03/2007 13:13:32
Thx for your replys.
We've allready tryed most of the suggested solutions. But thx for the input.
I tend to believe that it is an IIS configuration error.
We've allready tryed most of the suggested solutions. But thx for the input.
I tend to believe that it is an IIS configuration error.
You must be logged in to post in the forum