Reputation: 8151
Well I solved the problem of running out of memory when accessing the PDF files, but now it seems that when I try to access big files via Chrome or Firefox I get gibberish. It doesn't open Adobe, it just display it as a page with millions of characters. Im using the code below to get it to the user, any ideas on why it would be doing this?
case "PDF":
context.Response.ContentType = "application/pdf";
context.Response.AddHeader("content-disposition", "inline; filename=" + asset.A_Name);
}
context.Response.BinaryWrite(content);
Upvotes: 0
Views: 4572
Reputation: 3475
You have to add a content length header to the response. Its a problem with IIS chunked encoding. Look here.
context.Response.AddHeader("Content-Length", fileInfo.Length.ToString())
;
Upvotes: 4
Reputation: 11759
Has anything already been written to the Response stream? Make sure to call Response.Clear()
first.
Upvotes: 0