ashx

I am outputting a PDF file in a Web browser (IE8) HttpContext.Response.writefile(fileName) and it works great. When I try to save the file, it will give me the name of the ashx handler as a default. I would like to actually pass the real name. I tried to add header information as follow: context.Response.AddHeader("content-disposition", "attachment; filename=" + fileInfo.Name); And it works but I do not want the user to have to choose between open and save, i want the file to open normally and if the user chooses to save it then the dialog would give him/her the default filename. I tried also:

I'm requesting .ashx page from Master page client side script (Jquery) which has a code to download a PDF file. When I debug it, I can see the execution of "file download" code but file is not downloading. $.ajax({ type: "POST", url: "FileDownload.ashx", dataType: "html", success: function (data) { } } ); public class FileDownload : IHttpHandler { public void ProcessRequest(HttpContext context) { //context.Response.ContentType = "text/plain"; //context.Response.Write("Hello World"); string fileName = "BUSProjectCard.pdf"; string filePath = context.Server.MapPath("~/Print/"); context.Response

We are providing downloads of our application setups through an ASHX handler in ASP.NET. A customer told us he uses some third party download manager application and that our way of providing the files currently does not support the "resume" feature of his download manager application. My questions are: What are the basic ideas behind resuming a download? Is there a certain HTTP GET request that tells me the offset to start at? Resuming a download usually works through the HTTP Range header. For example, if a client wants only the second kilobyte of a file, it might send the header Range:

How can I use output caching with a .ashx handler? In this case I'm doing some heavy image processing and would like the handler to be cached for a minute or so. Also, does anyone have any recommendations on how to prevent dogpiling? There are some good sources but you want to cache you processing server side and client-side. Adding HTTP headers should help in the client side caching here are some Response headers to get started on.. You can spend hours tweaking them until you get the desired performance //Adds document content type context.Response.ContentType = currentDocument.MimeType;

$(document).ready(function() { $.ajax({ type: "POST", url: "/getprojects.ashx", data: "<formData client=\"\" year=\"\" categories=\"\" tags=\"\" freeText=\"\" count=\"34\" page=\"1\"></formData>", dataType: "text/xml", cache: false, error: function() { alert("No data found."); }, success: function(xml) { alert("it works"); alert($(xml).find("project")[0].attr("id")); } }); }); My problem is i get some data back but i can't seem to get it displayed. dataType should be the type of what you receive but contentType should be the mime-type of what you are sending, the following should be ok: $

I have the following image in my aspx page <td> <asp:Image ID="LargeImage" runat="server" Height="100" Width="100" />" </td> In my aspx.cs, assigned a imageurl to this image protected void uploadimage_Click(object sender, System.EventArgs e) { ImageUtils.uploadImage(Titletxt.Text, FileUpload.FileContent); LargeImage.ImageUrl = "~/AvatarImageFetch.ashx?memberid=" + memberid.ToString(); } For some reason, the image doesn't show up. Here's my ashx public void ProcessRequest(HttpContext context) { SqlConnection myConnection = new SqlConnection(System.Configuration.ConfigurationManager