H
Harry Whitehouse
I wrote a newbee ASPX application which allows authenticated users to
download a fairly large file (10 MB). After authentication in a simple SQL
table and picking what file the user will get, I give the commands shown
below. This works pretty well for folks on broadband, but dial-up users
tend to have the download interrupted after about 8-10 minutes.
Are there any session time out parameters I've forgotten to set? If
multiple users hit this page at the same time and are downloading the same
file, will this ASPX solution be somehow compromised?
TIA
Harry
Response.Clear();
Response.ClearHeaders();
Response.ClearContent();
Response.AddHeader("content-disposition","attachment; filename=" + myfile);
Response.AppendHeader("Content-Length", size.ToString());
Response.ContentType = "application/octet-stream";
Response.WriteFile(filename);
Response.End();
download a fairly large file (10 MB). After authentication in a simple SQL
table and picking what file the user will get, I give the commands shown
below. This works pretty well for folks on broadband, but dial-up users
tend to have the download interrupted after about 8-10 minutes.
Are there any session time out parameters I've forgotten to set? If
multiple users hit this page at the same time and are downloading the same
file, will this ASPX solution be somehow compromised?
TIA
Harry
Response.Clear();
Response.ClearHeaders();
Response.ClearContent();
Response.AddHeader("content-disposition","attachment; filename=" + myfile);
Response.AppendHeader("Content-Length", size.ToString());
Response.ContentType = "application/octet-stream";
Response.WriteFile(filename);
Response.End();