Fetch request middleware in kestrel returning net::ERR_INCOMPLETE_CHUNKED_ENCODING

Question

I am trying to resolve two errors on my kestrel middleware which is designed to handle a fetch request and return some JSON. (I am not interested in using MVC)

The code works, but I would like to remove these two errors:

In chrome I get this error:

net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK)

In kestrel I get this error:

"statuscode cannot be set because the response has already started"

        public void Configure(
            IApplicationBuilder app,
            IHostingEnvironment env,
            ILoggerFactory loggerFactory)
            {
    // some startup stuff...

        app.Use(async (context, next) =>
                {
                    if (context.Request.Path.HasValue && context.Request.Path.Value.Contains("searchjsfetch/"))
                    {
                        await context.Response.WriteAsync(JsonConvert.SerializeObject(simpleObject), Encoding.UTF8);
                    }
    })
}

In typescript I fetch like this:

fetch(`${hostDomain}searchjsfetch/${email}/2/3`)
                    .then((response) => {
                    response.body.getReader().read().then((c) => {
                            return new TextDecoder("utf-8").decode(c.value);
                        });
                    })

What is it you're expecting to fetch? Middleware would be something you can inject into the request/response pipeline, but typically you wouldn't be handling a complete request with only middleware. — Tony Ranieri, Mar 18 '19 at 19:25
Can you elaborate on what your concerns are with MVC that make you want to avoid it? — Tony Ranieri, Mar 18 '19 at 19:45

score 0 · Answer 1 · answered Mar 18 '19 at 19:52

With ASP.NET Core, you will "use MVC" (eg: in your startup.cs), but that doesn't mean you have to use MVC (views, etc)... You'll be using MVC namespaces, etc, but you can still return JSON data. There are a couple classes that are aimed at APIs than a traditional MVC view response -

The first would be ControllerBase - https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase?view=aspnetcore-2.2

The second class that may be of interest would be the ApiControllerAttribute class

Take a look at this article - https://learn.microsoft.com/en-us/aspnet/core/web-api/?view=aspnetcore-2.2

I figured out how to do it without MVC if you're interested – patrick Mar 19 '19 at 17:45 — patrick, Mar 19 '19 at 17:45

score 0 · Accepted Answer · answered Mar 19 '19 at 17:45

0

Well that was dumb, I had an extra

await next();

Which caused the problems

answered Mar 19 '19 at 17:45

patrick

16,091
29
100
164

Fetch request middleware in kestrel returning net::ERR_INCOMPLETE_CHUNKED_ENCODING

2 Answers2