I’m cruising through building the third iteration of my website, and an interesting thing just happened that got me thinking.
I’m working offline, and then load up a working version onto my website. When I go to view it, I notice that the new version isn’t loading, it’s the old cached version. Even if I refresh it still loads the cached version. Once I clean my browser catch it finally loads the latest version.
Obviously this is bad, because once it’s live, if people don’t clean their cache religiously, the old version will pop up. (say I add a new download or something) I don’t recall having this problem with my last one, and since I’ve designed this one slightly differently I’m wondering what the deal is.
Old website - A simple “shell” with an iframe in the middle that loads news.html I then only have to maintain the news.html instead of editing the shell html, because it’s filled with tables and other garbage.
New website - Again, a simple shell, this time with 4 windows each with it’s own iframe. The goal was the same, maintain a few simple html files that were plugged into the iframes. I had diffiiculty with some sizing and dreaded scroll bars, so I ditched the iframes and plugged the html directly into the main page. Now I only have 1 html file, which while inelegantly coded, works nice.
Anyway, my long winded question is this. Did I not have a cache problem with my old site because the page would load (the cached “shell”) and then load the iframes (which weren’t cached)? Since the new site is only one html page that is already cached, what is the work around? IIRC there’s a way to bypass the cache and have it load new each time. Should I do it that way?
Sorry this was so long winded.
Old site - http://www.subtechbeats.com/oldindex.htm
New site - http://www.subtechbeats.com/master.htm