ASP.NET InputStream is not a stream

[Steve Drake]

All,

I have a HttpHandler that handles a PUT, if i PUT 700MEGs of data it runs
out of memory, i have found that this is due to the Request.InputSt ream
loading the entire stream when you access it.

If I run any of the following i get the error :

Context.Request .SaveAs(@"C:\1. xxx",false); // I get out of memory

System.Diagnost ics.Trace.Write Line(Context.Re quest.InputStre am.CanRead); //
I get out of memory

byte[] data = new byte[4096];
data = Context.Request .BinaryRead(409 6); // I get out of memory

Cheers

Steve

[bruce barker]

turn page buffering off.

Page.ResponseBu fferOutput = false;

note: this will tie up an asp.net thread, and 2 communication threads until
completed. if you have many concurrent downloads you will quickly get a
server busy error.
-- bruce (sqlwork.com)

"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:%2******** **********@TK2M SFTNGP09.phx.gb l...

All,

I have a HttpHandler that handles a PUT, if i PUT 700MEGs of data it runs
out of memory, i have found that this is due to the Request.InputSt ream
loading the entire stream when you access it.

If I run any of the following i get the error :

Context.Request .SaveAs(@"C:\1. xxx",false); // I get out of memory

System.Diagnost ics.Trace.Write Line(Context.Re quest.InputStre am.CanRead); // I get out of memory

byte[] data = new byte[4096];
data = Context.Request .BinaryRead(409 6); // I get out of memory

Cheers

Steve

[John Saunders]

"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:%2******** **********@TK2M SFTNGP09.phx.gb l...

All,

I have a HttpHandler that handles a PUT, if i PUT 700MEGs of data it runs
out of memory, i have found that this is due to the Request.InputSt ream
loading the entire stream when you access it.

Write an asynchronous handler.
--

-----
John Saunders

[Steve Drake]

the request stream does not have the options of turning off this buffer.

but... i did try to see if it affected the request stream, and it still runs
out of memory.

Steve
"bruce barker" <no***********@ safeco.com> wrote in message
news:#C******** *****@TK2MSFTNG P15.phx.gbl...

turn page buffering off.

Page.ResponseBu fferOutput = false;

note: this will tie up an asp.net thread, and 2 communication threads until completed. if you have many concurrent downloads you will quickly get a
server busy error.
-- bruce (sqlwork.com)

"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:%2******** **********@TK2M SFTNGP09.phx.gb l...

All,

I have a HttpHandler that handles a PUT, if i PUT 700MEGs of data it runs out of memory, i have found that this is due to the Request.InputSt ream
loading the entire stream when you access it.

If I run any of the following i get the error :

Context.Request .SaveAs(@"C:\1. xxx",false); // I get out of memory

System.Diagnost ics.Trace.Write Line(Context.Re quest.InputStre am.CanRead);

//

I get out of memory

byte[] data = new byte[4096];
data = Context.Request .BinaryRead(409 6); // I get out of memory

Cheers

Steve

[Steve Drake]

I get the same problem.

I have managed to reproduce this in a test app create a web project , call
it LargePUTTEST

I've done it with a async class but the real app is not. I don't think this
will matter.

Confgure IIS

Add VERB PUT to ASPX (Right click on APP in IIS, click configure, select
..ASPX, add put to list of verbs, eg change GET,HEAD,POST,D EBUG,OPTIONS to
GET,HEAD,POST,D EBUG,OPTIONS,PU T

Add this to the page load

private void Page_Load(objec t sender, System.EventArg s e)
{
System.IO.Strea m RequestStream;
System.Net.Http WebRequest Request =
(System.Net.Htt pWebRequest)Sys tem.Net.HttpWeb Request.Create( "http://localhos
t/LargePUTTest/test.aspx");
Request.Method = "PUT";
Request.Content Length = 1024 * 1024 * 1024;// 1 GIGish some people says
its 1024 * 1024 * 1000 :)
RequestStream = Request.GetRequ estStream();
byte[] data = new byte[4096];
for(int i=0;i<Request.C ontentLength;i+ =4096)
RequestStream.W rite(data,0,409 6);
RequestStream.C lose();
}

Add this file (name httpHandler.cs)

using System;
using System.Web;

namespace LargePUTTest
{
/// <summary>
/// Summary description for httpHandlers.
/// </summary>
public class httpHandler :IHttpAsyncHand ler
{
public httpHandler()
{
//
// TODO: Add constructor logic here
//
}
#region IHttpAsyncHandl er Members

public IAsyncResult BeginProcessReq uest(HttpContex t context,
System.AsyncCal lback cb, object extraData)
{
// TODO: Add httpHandlers.Be ginProcessReque st implementation
System.Diagnost ics.Trace.Write Line(context.Re quest.InputStre am.CanRead);
// this causes the out of memory.
return null;
}

public void EndProcessReque st(IAsyncResult result)
{
// TODO: Add httpHandlers.En dProcessRequest implementation
}

#endregion

#region IHttpHandler Members

public void ProcessRequest( HttpContext context)
{
// TODO: Add httpHandlers.Pr ocessRequest implementation
}

public bool IsReusable
{
get
{
// TODO: Add httpHandlers.Is Reusable getter implementation
return false;
}
}

#endregion
}
}

[Steve Drake]

I have logged this as a support call, and MS says that it copies the Request
stream into memory so you will get out of memory exceptions and there is now
way round it.

I consider this poor design.

Steve
"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:#F******** ******@TK2MSFTN GP09.phx.gbl...

All,

I have a HttpHandler that handles a PUT, if i PUT 700MEGs of data it runs
out of memory, i have found that this is due to the Request.InputSt ream
loading the entire stream when you access it.

If I run any of the following i get the error :

Context.Request .SaveAs(@"C:\1. xxx",false); // I get out of memory

System.Diagnost ics.Trace.Write Line(Context.Re quest.InputStre am.CanRead); // I get out of memory

byte[] data = new byte[4096];
data = Context.Request .BinaryRead(409 6); // I get out of memory

Cheers

Steve

[John Saunders]

"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:eZ******** ******@TK2MSFTN GP14.phx.gbl...

I get the same problem.

Steve, what happens if your BeginProcessReq uest method just does a
inputStream.Beg inRead(...)?
--

-----
John Saunders

[Gabe Garza]

Steve,

I'd write an ISAPI and either do a IO Completion using HSE_REQ_IO_COMP LETION
or just use EXTENSION_CONTR OL_BLOCK *pEcb->ReadClient() to keep reading data
coming from the client until your 700 Meg file has been uploaded.

This will get you what you want, a stream.

Gabe

"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I have logged this as a support call, and MS says that it copies the Request stream into memory so you will get out of memory exceptions and there is now way round it.

I consider this poor design.

Steve
"Steve Drake" <Steve@_NOSPAM_ .Drakey.co.uk> wrote in message
news:#F******** ******@TK2MSFTN GP09.phx.gbl...

All,

I have a HttpHandler that handles a PUT, if i PUT 700MEGs of data it runs out of memory, i have found that this is due to the Request.InputSt ream
loading the entire stream when you access it.

If I run any of the following i get the error :

Context.Request .SaveAs(@"C:\1. xxx",false); // I get out of memory

System.Diagnost ics.Trace.Write Line(Context.Re quest.InputStre am.CanRead);

//

I get out of memory

byte[] data = new byte[4096];
data = Context.Request .BinaryRead(409 6); // I get out of memory

Cheers

Steve