Env: Win2K Server SP4, IIS 5.0

I want to send very large data post to IIS from a client. On IIS, i am
using an ASP page for testing purposes. See below.
The behavior that I am seeing from a java clinet client is that the socket
is being close by the server after approximately 300 - 400 meg or so.

Is there may be a metabase setting somewhere in IIS ? or is there a
restriction in IIS ?



<%

Dim ByteCount, BinRead, totalRead, chunkSize
Dim iteration

totalRead = 0
interation = 0
chunkSize = 8192


ByteCount = Request.TotalBytes

Response.write "Total bytes " & ByteCount
while (totalRead < ByteCount)


if (ByteCount - totalRead >= 8192) then
chunk = 8192
else
chunk = ByteCount - totalRead
end if

dim data
data = Request.BinaryRead ( chunk )
interation = interation + 1
totalRead = totalRead + chunk

Response.write "Total bytes read is " & totalRead
wend

Response.write "Total bytes read is " & totalRead & ". Iteration count
is " & iteration

%>

RE: Large data Post to IIS causing premature socket close by v-wzhang

v-wzhang
Thu Jul 01 03:27:14 CDT 2004

Hi,

On IIS6 there is a metabase key - AspMaxRequestEntityAllowed to
control the POST size to ASP page. By default the setting is only
200K.

However, this key isn't set on IIS5(Win2K SP4) machine and doesn't
exist on IIS5(Before SP4). So the hard-coded limitation of HTTP POST
is very large on IIS5 - more than 1 GB is still workable.

To successfully run this page with more than 400M post size, please
first check if there is any special ISAPI filter installed in W3SVC
global setting(e.g URLScan). In IIS mmc, open the server(computer
icon)'s property in WWW Service->ISAPI Filters, check the filters.

Second, I found with a 400M file posted, the ASP script was running
very slow(more than 5 mins on my test machine) and timed out before I
increased ASP script timeout setting. Please use MetaEdit to edit
your metabase and increase the AspScriptTimeout property value under
W3SVC node, the default setting is 90 sec.

If it's still failed, check the latest IIS log record(
\WINNT\system32\LogFiles\W3SVC[x] ) to determine what the problem is.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security