Uploading Large Files

[=?Utf-8?B?RGFu?=]

MS won't seem to let me reply to my old post, so I created a new one.

The error occurs in all browsers. It's definitely a server issue, not client.
The server is not proxied in any way.
I tried uploading the files on the server and experienced the same issues as
I get on any other computer.

Thanks in advance for your help.
Dan

In reply to Dave Anderson, who was in reply to me:

When uploading about 20mb worth (10x2mb files), I get the following
error (thrown from firefox). I tried changing Response.Expire s,
Server.ScriptTi meout, and the connection timeout setting for the
website in IIS.

Is Firefox the only affected browser?

Connection Interrupted
The connection to the server was reset while the page was loading.
The network link was interrupted while negotiating a connection.
Please try again.
>
When uploading about 2-10mb worth of files, I get an error thrown by
ASP. The error typically just means that AspMaxRequestEn tityAllowed
needs to be increased, but since I've already increased it as high as
it can go, I'm really confused.

Is there any chance this server is behind a proxy (reverse or otherwise)?
Can you duplicate this behavior on the server itself (by logging into the
server and using the web client on the machine to upload a large file)?

[Dave Anderson]

Re: Uploading Large Files

"Dan" wrote:

The error occurs in all browsers. It's definitely a server issue,
not client. The server is not proxied in any way.
I tried uploading the files on the server and experienced the same
issues as I get on any other computer.

OK. We went through something similar a couple of years ago, but I don't
recall the exact filesize aperture. I thought it was higher than 6MB, but I
could be remembering wrong.

We were looking for a classic ASP solution because we were not interested in
re-writing the rest of the application in ASP.NET.

Our solution was a hybrid -- one ASHX file for handling the file upload,
then redirecting to an ASP page. This got us completely around the limit --
I have tested with 100MB+ files. It requires that the uploaded files be
parked somewhere temporary; we stick the files in a SQL Server table for
consumption by ASP scripts further down the line (these either write the
file to disk or transfer it to another table/db). Every uploaded file
expires and is automatically cleaned from our table.

I would be happy to give you some pointers in that direction, should you
decide it is worth a look.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.