Here's the problem:
The site for my company has just updated a page to remove "sensitive" items from it for a client. People at the client's site surf to the page and see the old one in their cache, not the new one on our server, and do not seem to be able to grasp the concept of browsers caching web pages and the fact that the page only exists on their own hard drives.
How can either our web page or our Apache web server force someone's browser to view the new page and not the old cached one? <META> tags seem to be one answer, though not a very good one. Another server-side solution seems to be redirection, though I dunno if it would introduce a bug to have someone redirected to a new version of the same page.
Any input would be wildly appreciated. I know little about hosting a site, but since I'm the "IT guy" here this falls to me, and the page is totally offline until I can fix it.
The site for my company has just updated a page to remove "sensitive" items from it for a client. People at the client's site surf to the page and see the old one in their cache, not the new one on our server, and do not seem to be able to grasp the concept of browsers caching web pages and the fact that the page only exists on their own hard drives.
How can either our web page or our Apache web server force someone's browser to view the new page and not the old cached one? <META> tags seem to be one answer, though not a very good one. Another server-side solution seems to be redirection, though I dunno if it would introduce a bug to have someone redirected to a new version of the same page.
Any input would be wildly appreciated. I know little about hosting a site, but since I'm the "IT guy" here this falls to me, and the page is totally offline until I can fix it.