We're doing a Server.Transfer from one .aspx page to another .aspx web page. The second .aspx page response.clear()'s the buffer, response.writefile()'s a PDF/DOC/or XLS document from disk into the response buffer, sets the right http headers depending on the doc type, and then Response.End()'s to return the document in the browser to the end-user in a way that invokes the Acrobat, Word or Excel helper app within the browser window.
The issue is that the browser history doesn't seem to be updated, so when the user presses the back button, they go back two actual pages rather than going back to the preceding page the document was launched from. On the other hand, if we do a Server.Transfer to a .aspx page that renders itself as a normal .aspx page, the browser history is updated just fine and back goes back 1 page as it should. I've been looking for a way to alleviate this. Any ideas? This may be a http question as much as it is an ASP.NET question. Thanks, Kyle Clarke [EMAIL PROTECTED] You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
