File Download Times Out On Slow Connections

[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();

[Andy Fish]

I don't think it can be anything to do with session, because you're just
talking about a single HTTP request.

is it perhaps your page execution timeout?

http://msdn.microsoft.com/library/de...imesection.asp
"Harry Whitehouse" <ha***@envmgr.com> wrote in message
news:Od**************@TK2MSFTNGP12.phx.gbl...

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();

[Harry Whitehouse]

Andy -- Thanks for this hint! That page also linked to an article about
downloading large files which I also applied to my application:

http://support.microsoft.com/?id=812406

Best

Harry

[Andy Fish]

"Harry Whitehouse" <ha***@envmgr.com> wrote in message news:<u6**************@TK2MSFTNGP11.phx.gbl>...

Andy -- Thanks for this hint! That page also linked to an article about
downloading large files which I also applied to my application:

http://support.microsoft.com/?id=812406

hey thanks for that link, That's a problem that I could well hit in
some work I'm doing.

I have to say that just sucks big time - providing a special API to
send a file and then implementing it so it reads the whole file into
memory - D'oh!


Best

Harry