I know there are lots of similar questions, but a tricky idea has come to my mind.
It is known that a download HttpContext.Current.Response.AddHeader("Content-Disposition", "attachment")
can stop the browser from refreshing page, because a download itself is a response and a refreshed page cannot be generated as another response. Of course I'm not going to make a download just to get rid of page refresh, but I'm thinking of if there is any other form of HTTP response that can 'replace' the page refresh, or any method of HttpContext.Current.Response
that can clear the default response. Any idea?
(Don't ask me why it has to be without AJAX. I know it can work. Just not preferred at the moment)