Sending a file via HttpContext makes the browser hang

I am sending a file to the user using HttpHandler. In all browsers, after viewing / downloading a file at least once, the browser / application freezes on subsequent views / downloads. Here is the code:

    private void TransmitFile(HttpContext context, string filePath, string downloadName, bool forceDownload)
    {
        if (File.Exists(filePath))
        {
            string fileName = System.IO.Path.GetFileName(filePath);
            string extension = Path.GetExtension(filePath);
            FileInfo fileInfo = new FileInfo(filePath);

            // set the response info/headers
            context.Response.ClearContent();
            context.Response.ClearHeaders();
            context.Response.AddHeader("Content-Length", fileInfo.Length.ToString());
            if (forceDownload)
            {
                context.Response.AddHeader("Content-Disposition", "attachment; filename=" + downloadName.Replace(" ", "_") + extension);
                context.Response.BufferOutput = false;
            }

            string type = "";
            // set known types based on file extension  
            if (extension != null)
            {
                switch (extension.ToLower())
                {
                    case ".tif":
                    case ".tiff":
                        type = "image/tiff";
                        break;
                    case ".jpg":
                    case ".jpeg":
                        type = "image/jpeg";
                        break;
                    case ".gif":
                        type = "image/gif";
                        break;
                    case ".doc":
                    case ".rtf":
                        type = "Application/msword";
                        break;
                    case "pdf":
                        type = "Application/pdf";
                        break;
                    case "png":
                        type = "image/png";
                        break;
                    case "bmp":
                        type = "image/bmp";
                        break;
                    default:
                        type = "application/octet-stream";
                        break;
                }
            }

            context.Response.ContentType = type;
            context.Response.TransmitFile(filePath);
            context.Response.Flush();
        }
        else
        {
            Immersive.Diagnostics.Log.Warn("Requested file does not exist: " + filePath, this);
            Immersive.Diagnostics.Log.Warn("", this);
        }
    }

      

I read that calling Response.Close () and Response.End () is not a good idea? We tried both to leave and to delete, and it still happens.

EDIT:

It seems that TransmitFile knows the problems. A more detailed explanation can be found at: http://www.improve.dk/blog/2008/03/29/response-transmitfile-close-will-kill-your-application

I removed TransmitFile and changed it to WriteFile and now it works fine.

context.Response.WriteFile(filePath);
context.Response.Flush();
context.Response.Close();

      

+1


a source to share


2 answers


This may be a known issue if the server you are loading is running Windows Server 2003 SP1.

Here's the fix: http://support.microsoft.com/kb/902780



Also check if the page is there OutputCache

, if so, try downloading without it.

0


a source


For what reason are you not using buffering? You are Flush () even though you are not using it. And yes, I think you should also do Response.End () after Flush ().



Let me know if it works and maybe I can run some tests myself.

0


a source







All Articles