3 ms·
doesn't this mean when they end up on your 1997 site (without realizing it, because all they did was click a link), and then try to navigate around, they're stu
by woodrowbarlow 6y ago
doesn't this mean when they end up on your 1997 site (without realizing it, because all they did was click a link), and then try to navigate around, they're stuck in the old version of your site?
edit: maybe not, because the old site was written to assume it's running at the current site's subdomain? i guess it depends on much you've changed your URL structure since then. that thought makes me a little squeemish.
it seems like a nice approach would be to return the 404, and make your 404 page render a link that says "try an archived version?". you gotta let the user know that what they're about to see might be stale.
- grifball 6y agoYeah. I really like this idea of warning the user. Keep the usability without losing the functionality. Also, not sure if anyone is thinking of this, but there are security concerns if you were to serve up old pages on a new domain. If that old page has a vulnerability, it now has access to data in the new domain. This is more for archiving, so the old pages wont get patched.
- saalweachter 6y agoI could also see a 404 iFrame.
- ric2b 6y agoThat sounds much better, love the idea and it's almost as easy, just need a custom 404 page template.