I use the code below to authorise the download of certain files.

Thus, instead of linking to the file in a wwwroot directory, I link to

this code with the filename as a parameter, and the script streams the

file if the user is authorised.

This has worked fine on PDFs, DOCs, XLS, etc. until today, and 18MB

file presents the error message 'format error: not a pdf or corrupt'.

iporter wrote:

What do you mean by "presents the error message"? Is this a client-side

error or a server-side error?

If client-side, then you may need to examine things like your ASP output

buffer size and your script timeouts.

More than likely, you can solve this by writing in chunks. See the example

about halfway down this article:http://www.­aspfaq.com/show.asp?­id=2161

--

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.

On Mar 29, 7:46 pm, "Dave Anderson" <NYRUMTPEL...@spamm­otel.com>

wrote:

Cheers - resolution involved increasing the AspBufferingLimit in

Metabase.xml - see http://clearglass.n­et/index.php?p=10.

It has the advantage of using memory more effeciently on

the server by turning off buffering and chunking the file

to the response.

There is no need to modify the buffering limit from the

default 4MB when using this function.

"Anthony Jones" wrote:

Is that fact or speculation? I've never seen evidence that this is more

efficient on the server.

It's not a fact by observation but neither is it speculation.

Response.BinaryWrit­e doesn't return until all the buffer

contents have been sent.

I'll let you do the math.

Anthony Jones wrote:

Doesn't return what? From what? To what? This does not make any sense to

OK. In either case, the same amount of content has to be put into the

buffer, and the same amount written from the buffer. You don't even bother

to speculate about the cost of repeatedly using Stream.Read(bytes) over

Stream.Read(adReadA­ll). So absent the Urim and Thummim neccessary for

scrying the Response Object, there does not seem to be any "math" to do.

are *clearly* speculating.

I will grant this -- when combined with Response.isClientCo­nnected [1],

using the chunked method allows you to abort the process before the entire

Stream is dealt with, which seems at first glance like a decent idea for

sending very large files. But since your example ignores

you have not made any sort of "performance" case whatsoever.