Forum Moderators: not2easy
i updated my site <>
the update included changes in my css file.
after the update, i think the server is still using the old css,and not updating with the updated css.
everything is fine.
i tested by uploading the content to another domain i own <>, and on this site, the pages are loading fine.
what is wrong here? im using IIS 6.0 on win 2003.
i googled alot to find a solution, and i came across some workaround by editing the registry entries, such as UriEnableCache, did that. reseted iis, still, no luck.
something is causing the server to cache/load old version of my site.
any help will be appreciated.
Thanks
[edited by: SuzyUK at 10:50 am (utc) on Mar. 14, 2007]
[edit reason] No site specifics, thanks. See TOS #13 [WebmasterWorld.com] [/edit]
your old stylesheet is probably being cached hit CTRL+F5 on your browser
if the site has been online for a while and you think your users might have the same problem, then rename the stylesheet and also the update the link to it it your pages it will force a refresh
HTH
Suzy
thanks, after more than 24 hours of testing, and all, your suggestion of renaming the css file worked.
:)
Thanks
I have had this and similar problems many times. I have
pretty much fixed it by including the following in the
<head> section of every page I create or update.
<META http-equiv="Cache-control" content="no-cache">
<META http-equiv="Pragma" content="no-cache">
<META http-equiv="Expires" content="Thu, 01-Jan-2003
01:01:01 GMT">
This should turn off caching everywhere from the original
server through the final browser.
I don't feel that caching is of much use anymore. A
high percentage pages are dynamic, and even those that
are static aren't viewed by the same person, or even a
person at the same site, very frequently. Not like it
was when the WWW etc. was first conceived and implemented.
Unfortunately there isn't any way to preempt copies
currently in cache somewhere!
Good Luck!
Dennis
I don't feel that caching is of much use anymore.
Well, that is certainly debatable - and very much dependant on the type of site you have. But also bear in mind that with caching disabled, your sites' bandwidth is likely to increase (maybe a lot) too.
To get around 'the caching problem' of an external CSS / JS file, you could also *try* appending a dummy querystring to the end of the filename (change it when you make an update)...
<link rel="stylesheet" type="text/css" href="mystyle.css?14032007">
The browser should see it as a new request, since "mystyle.css?14032007" won't be a reference in the cache, but it won't effect the filename "mystyle.css".
