server.transfer

I avoid the default ASP.NET approach of redirecting on errors (as many people do). Clean AJAX code and SEO are among the reasons. However, I'm using the following method to do it, and it seems that I may lose HttpContext.Current.Items in the transfer? <httpErrors errorMode="Custom" existingResponse="Replace"> <remove statusCode="401" /> <remove statusCode="403" /> <remove statusCode="404" /> <remove statusCode="500" /> <error statusCode="401" responseMode="ExecuteURL" path="/Account/SignIn" /> <error statusCode="403" responseMode="ExecuteURL" path="/Site/Forbidden" /> <error statusCode="404"

I'm using an .aspx page to serve an image file from the file system according to the given parameters. Server.Transfer(imageFilePath); When this code runs, the image is served, but no Last-Modified HTTP Header is created. as opposed to that same file, being called directly from the URL on the same Server. Therefor the browser doesn't issue an If-Modified-Since and doesn't cache the response. Is there a way to make the server create the HTTP Headers like normally does with a direct request of a file (image in that case) or do I have to manually create the headers? When you make a transfer to

I am using Server.Transfer . Everything works fine, but exception log shows following exception. System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort(Object stateInfo) at System.Web.HttpResponse.End() at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm) at System.Web.HttpServerUtility.Transfer(String path) Any idea to avoid above exception. This exception is throw by the call to Server.Transfer in order to halt the execution of the current method - exactly the same thing gets thrown

I have a HttpModule in C# 2.0 which handles exceptions thrown. Whenever the exception is thrown, an error page (aspx) with some querystring will be called. It is done through Server.Transfer() . But when the control tries to execute Server.Transfer() , the following exception is thrown: Error executing child request for [pagename].aspx. Whereas Request.Redirect() works fine. I tried setting EnableViewStateMac="false" in Page directive of the page to which request is transferred. Still problem persists. Here is the code I tried: string errorPage = "errorpage.aspx?id=" + someErrorId HttpContext

What is difference between Server.Transfer and Response.Redirect ? What are advantages and disadvantages of each? When is one appropriate over the other? When is one not appropriate? CMS Response.Redirect simply sends a message (HTTP 302) down to the browser. Server.Transfer happens without the browser knowing anything, the browser request a page, but the server returns the content of another. Christian Payne Response.Redirect() will send you to a new page, update the address bar and add it to the Browser History. On your browser you can click back. Server.Transfer() does not change the