Unable to access twice to request.InputStream

[bufferUnderrun]

How to reproduce (in the ResApiSample.cs) :

            [WebApiHandler(HttpVerbs.Post, RelativePath + "people/*")]
            public async Task<bool> PostPeople(WebServer server, HttpListenerContext context)
            {
                    ...
                    var post = context.RequestFormData(); // OK
                    var model = context.ParseJson<GridDataRequest>(); // will be null
                    ...
            }

OR

            [WebApiHandler(HttpVerbs.Post, RelativePath + "people/*")]
            public async Task<bool> PostPeople(WebServer server, HttpListenerContext context)
            {
                    ...
                    var model = context.ParseJson<GridDataRequest>(); // OK
                    var post = context.RequestFormData(); // will be null
                    ...
            }

The problem come from the underlying inputStream : when StreamReader is disposed, it lets the cursor position to the end. So the next call to StreamReader(inputStream) will be null.

         using (var body = request.InputStream) {
                using (var reader = new StreamReader(body, request.ContentEncoding)) {
                    var stringData = reader.ReadToEnd();

                    if (string.IsNullOrWhiteSpace(stringData)) return null;
                    return stringData.Split('&')
                        .ToDictionary(c => c.Split('=')[0],
                            c => WebUtility.UrlDecode(c.Split('=')[1]));
                }
            }

I've tried to use Read(pos, len) or force body.Position = 0 but this stream cannot be seek or written. Same problem using a MemoryStream and CopyTo... Do you have an idea to fix it ?

[geoperez]

Let me take a look in your sample.

[mariodivece]

This is most likely the underlying design of the http.sys implementation as the backing http stream is not rewindable for obvious reasons but thanks for checking @geoperez

[bufferUnderrun]

@mariodivece agree. Do you plan to cache context.Request.InputStream in order multiple reads works or keep the actual implementation ?

For instance, i've made a temporary workaround, so i can :

            [WebApiHandler(HttpVerbs.Post, RelativePath + "people/*")]
            public async Task<bool> PostPeople(WebServer server, HttpListenerContext context)
            {
                    ...
                    var body = context.RequestBody(); // just one call to inputStream
                    var model = context.ParseJson<GridDataRequest>(body); // ok
                    var post = body.FormData(); // ok
                    ...
            }

A bit verbose but solve my problem...

[mariodivece]

I have added the overloads. Hope these help. We will be releasing a new NuGet package if no more issues arise by the EOD.