Newcomsas wrote:
On a Windows 2000 - IIS 5 server we're running an ASP Classic
application that features an upload form for files of great
dimensions (100+MB). Problem is, when we try to upload a file
exceeding 3MB we retive almost immediatly a message such as
'The page cannot be displayed'.
We do not even reach the page that contains the code for file
managing; when we click on the submit button in the form with
enctype multipart form data the application ends and the error
is visualized.
For files under 3MB there are no problems at all.
The FAQ of our upload third party component (ABCUpload by
Websupergoo) state that we could either have problems with
our proxy or we could be stopped by a wrong URLScan setting:
we do not have any proxy nor URLScan is installed on our server.
I may add that all the configuration of the script timeouts on
IIS are correctly set.
It does not appear that IIS 5 is the problem -- I just uploaded an 80MB file
to one of our IIS 5 servers to be sure -- although you may want to examine
your metabase value for AspSessionMax. I am not sure whether your component
is affected by the metabase value, however.
We recently set out to free ourselves from dependence on upload components,
and settled on an ASP.NET 2.0 solution. We even designed it for integration
with classic ASP applications -- and have found it to be a very flexible
approach.
[off-topic]
My only real quibble with the ASP.NET approach concerns error handling.
Suppose you want to limit uploads to 64MB. Then you would put this in your
web.config, right?
<httpRuntime maxRequestLength="65536" ... />
That depends on whether you want or need access to the rest of the form
submission for such things as error messaging. If the upload exceeds the
maxRequestLength, the error falls into the Application_Error scope, not the
Page_Error. This means two things:
1. You can't use try...catch and gracefully reject based on filesize
2. When you DO handle the error, you lose access to all of the
useful parts of the HttpRequest, such as the Form items.
One alternative is to really crank up maxRequestLength, but then you have to
allow very large uploads to complete simply for the purpose of rejecting
them.
--
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.
