caching - chrome cache persisting old site -


going live new site today ran strange issue on chrome:

we changed dns point new server new site, , chrome seemed have cached old index.html file, none of srcs or includes.. rendered text old index.html generated 404s on css , imgs.. , displayed ugly mess.

i hacked workaround: locating js file old index file looking injected new js file redirected call "index.html" instead of "/" , resolved it, ugly temporary flash of hideous mess cached index file.

everything googled told me how flush cache, i'm not concerned how browser reads site, i'm concerned how others browsers read site. tried putting no-cache tag in no avail.. read later chrome ignores tag...

anyone encounter before , have better solution??

update: in case else stumbles similar situation. looks old site had cache setting in web.config. nitin suggesting logs. examining network traffic in dev tools see cached retrieve, , more importantly cache control response header led me start examining files on old site.

lesson learned: , remove cache settings before going live new site.


Comments

Popular posts from this blog

javascript - jQuery: Add class depending on URL in the best way -

caching - How to check if a url path exists in the service worker cache -

Redirect to a HTTPS version using .htaccess -