I wrote: >> 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.
On Thu, 16 May 2002 09:46:05 -0400, Marsh, Drew <[EMAIL PROTECTED]> wrote: >But the history entry is for first.aspx right? I don't see how it could be >anything else, because, as I said, Server.Transfer is completely server side >and the client has no idea second.aspx is even being used. What Content- Type >are you specifying for the PDF/DOC/XLS responses? I'm using "application/pdf", "application/vnd.ms-excel" and "application/msword". >Does the browser have >handlers installed for these types or are they being offered for download. The browser (IE) invokes Acrobat, Word or Excel depending on the download and displays the document inside the browser (with the helper toolbar included). I think that means the handlers must be there. >The only explination I can think of for the difference in behavior is that >the transfer to an ASPX results in HTML which the browser can display and >thus it records in history, whereas if the browser doesn't have a handler >for the content type then all it can do is download it and I don't think it >will record a history entry for types it can't display. My big find today is that in Netscape (6.2) the browser behaves the way I would expect it to, whether the server-side redirect is to a .aspx page rendered as html, or to a .aspx page that response.writefiles a PDF/XLS/DOC. In IE, when I go to a plain .html page that has a link to a PDF and open it, the browser history is stored correctly; I can go "back" to the page I launched the PDF from. When I do a server-side redirect, if it's to another .aspx page the browser knows enough to update the history. If it's to a PDF/DOC/XLS that I return via Response.WriteFile() from that page, so far it seems not to be. So, my conclusion now is that it's an IE bug. Thanks! Kyle >HTH, >Drew >.NET MVP You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
