Can't download files > 4MB

[Wade]

We have an intranet web site set up to download (via http) files from a
server. If someone using IE trys to download either by clicking the link to
the file location or by right clicking the link and click Save Target As...
then they get the error message that "this page cannot be displayed...there
is a problem with the page you are trying to open..." And the address bar
show the ASP file that is performing the download.

File downloads work fine for any file that is below 4 MB, but the problem
happens for those above 4MB in size with 2 exceptions.

Exception 1 - my computer works fine -- even for a 100MB file I get the File
Download dialog box
Exception 2 - if someone uses firefox it works fine, but if that person uses
IE on the same computer the error shows up.

There appears to be some limit on http download size for IE and somehow on
my computer this limit has been increased or disabled.

Any idea where we can find this limiting factor?

Thanks.

 

[Wade]

Update...

After further testing, the two exceptions are false also. It does not
download to my computer it just gives a different error message - the first
dialog (File Download - Security Warning) comes up on mine, whereas it
doesn't come up on others, and the next dialog (after clicking Save on the
first) just sits for awhile, then says that the connection was reset and
never downloads. It never asks where I want to save the file.

It also does not download using FireFox. All of Firefoxes dialogs indicate
that the file downloaded sucessfully, but when checking the location of
where the file was downloaded, the file size is only 1K - not the 4MB+ size
it should be.

In both cases if the file is less than 4MB (4194304 bytes), everything works
fine. Now I'm thinking there must be something wrong in the ASP file that
performs the download...something to do with the stream maybe. Maybe the
stream buffer is limited. This probably isn't the newgroup to ask, but does
anyone here have any thoughts on this?

Thanks.

 

[Wade]

It was a buffer size issue in the ASP file. Nothing to do with IE or
FireFox.