I have an aspx page on a hosted server that executes a Response.Redirect to another page on my site. I've updated the called page but the Response.Redirect still has the client browser return the old page. If I put a URL for the called page directly into the client browser then the new page is executed. So there appears to be a cache somewhere that the Response.Redirect call pulls data from but that isn't accessed when the client directly puts the URL into the browser. I've been sure to clear the client browser cache before every call and even rebooted the client machine, so I'm sure the cache isn't in the client. It acts as if there's a cache on the hosting server that Response.Redirect calls access before sending the request all the way back to the client. Does anyone know what might be going on here?
Thanks for any ideas.