file size limit in Response.binary write

[S N]

I am using the following code to hide the download url of files on my website. The code uses Response.Binary write to send file to the client.
Kindly indicate the maximum size of the file that can be downloaded using this method.
I am hosting this site on a public server, so I will not be able to change anything on the webserver. Kindly indicate what can be done to ensure that the above method remains valid for any file size download.

call Response.AddHea der("Content-Disposition","a ttachment; filename=""" & strFileSave & """")
Response.Conten tType = "bad/type"
Set Fsys = Server.CreateOb ject("Scripting .FileSystemObje ct")
Set TS = Fsys.GetFile(st rFile).OpenAsTe xtStream(1, -1)
Do While Not (TS.AtEndOfStre am)
Response.Binary Write(TS.Read(1 ))
Loop

[S N]

Also advise the content type in case the file is an excel file, word
document, exe file, zip file etc.

Thanks in advance.
"Anthony Jones" <An***********@ yadayadayada.co mwrote in message
news:e9******** ******@TK2MSFTN GP02.phx.gbl...

"S N" <ua******@yahoo .comwrote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..

>What if we want to use sendfiletorespo nse but dont want to force the save
as dialog, instead just want to see the pdf file within the browser
window itself.
is there any change required in the code to achieve this.

If you know its a pdf then change content-type to application/pdf and
remove the attachment; keyword from content-disposition.

--
Anthony Jones - MVP ASP/ASP.NET

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

"S N" wrote:

Just one clarification
You intended
For i = 1 To oStream.Size / clChunkSize
or
For i = 1 To oStream.Size \ clChunkSize

He *intended* the latter.

The backslash operator means "integer division" in VBScript (and VB and
VB.NET) code.

That is,
a \ b
is equivalent to
INT( a / b )

*************** *****

Also, you don't need to mess with Response.Buffer =False, at all.

Just follow each
Response.Binary Write
with
Response.Flush

Now the buffer will never get more full than one "chunkSize" .

[Anthony Jones]

"Old Pedant" <Ol*******@disc ussions.microso ft.comwrote in message
news:85******** *************** ***********@mic rosoft.com...

>

"S N" wrote:

>Just one clarification
You intended
For i = 1 To oStream.Size / clChunkSize
or
For i = 1 To oStream.Size \ clChunkSize

He *intended* the latter.

The backslash operator means "integer division" in VBScript (and VB and
VB.NET) code.

That is,
a \ b
is equivalent to
INT( a / b )

*************** *****

Also, you don't need to mess with Response.Buffer =False, at all.

Just follow each
Response.Binary Write
with
Response.Flush

Now the buffer will never get more full than one "chunkSize" .

Yes that would work. However it would mask unintended errors that turning
the buffer off right at the top of the code exposes.

--
Anthony Jones - MVP ASP/ASP.NET

[S N]

"Anthony Jones" <An***********@ yadayadayada.co mwrote in message
news:us******** ******@TK2MSFTN GP05.phx.gbl...

"Old Pedant" <Ol*******@disc ussions.microso ft.comwrote in message
news:85******** *************** ***********@mic rosoft.com...

>>

"S N" wrote:

>>Just one clarification
You intended
For i = 1 To oStream.Size / clChunkSize
or
For i = 1 To oStream.Size \ clChunkSize

He *intended* the latter.

The backslash operator means "integer division" in VBScript (and VB and
VB.NET) code.

That is,
a \ b
is equivalent to
INT( a / b )

************** ******

Also, you don't need to mess with Response.Buffer =False, at all.

Just follow each
Response.Binary Write
with
Response.Flush

Now the buffer will never get more full than one "chunkSize" .

Yes that would work. However it would mask unintended errors that turning
the buffer off right at the top of the code exposes.

--
Anthony Jones - MVP ASP/ASP.NET

what kind of errors would be exposed by turning off the buffer. kindly
elaborate.

[Anthony Jones]

"S N" <ua******@yahoo .comwrote in message
news:OY******** *****@TK2MSFTNG P02.phx.gbl...

>
"Anthony Jones" <An***********@ yadayadayada.co mwrote in message
news:us******** ******@TK2MSFTN GP05.phx.gbl...

>"Old Pedant" <Ol*******@disc ussions.microso ft.comwrote in message
news:85******* *************** ************@mi crosoft.com...

>>>

"S N" wrote:

Just one clarification
You intended
For i = 1 To oStream.Size / clChunkSize
or
For i = 1 To oStream.Size \ clChunkSize

He *intended* the latter.

The backslash operator means "integer division" in VBScript (and VB and
VB.NET) code.

That is,
a \ b
is equivalent to
INT( a / b )

************* *******

Also, you don't need to mess with Response.Buffer =False, at all.

Just follow each
Response.Binary Write
with
Response.Flush

Now the buffer will never get more full than one "chunkSize" .

Yes that would work. However it would mask unintended errors that
turning the buffer off right at the top of the code exposes.

what kind of errors would be exposed by turning off the buffer. kindly
elaborate.

Well the sort of problems you've discovered where you may unintentionaly be
placing things in the output buffer that you didn't want present. Example:-

<!-- #include /virtual="/someinclude.asp " -->
<%
Response.Conten tType = "applicatio n/octet-stream"
Do Until ....
Response.Binary Write SomeStuff
Response.Flush
Loop
%>

'someinclude.as p

<!-- Ooops some accidental static content here -->
<%

'utility code

%>

Placing a Response.Buffer at the top of your page would barf immediately on
that line alerting you to a problem.
It also saves you having to remember to Response.Flush if you have multiple
places where you write to the buffer.

--
Anthony Jones - MVP ASP/ASP.NET