IIS in-proc changes some responses from content-length to chunked

[Tratcher]

Converting Content-Length responses to Chunked is problematic as clients may be expecting that content-length value.

Frequently reproduces with:

            ctx.Request.Headers.ContentLength = ctx.Request.Path.Value.Length;
            await ctx.Response.WriteAsync(ctx.Request.Path.Value);

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET
Date: Mon, 03 Jun 2019 16:13:19 GMT

2
/a

Reproduces less frequently with:

            ctx.Request.Headers.ContentLength = ctx.Request.Path.Value.Length;
            return ctx.Response.WriteAsync(ctx.Request.Path.Value);

@jkotalik

It's also known to change some auto-chunked responses to content-length, but that's less problematic as Content-Length is universally supported.

[kevinchalet]

Could that be related to this old bug? #9139

[Tratcher]

Perhaps, though I'm not setting a content-type.

[analogrelay]

Frequently reproduces with: ...
Reproduces less frequently with: ...

Umm... Am I not seeing how these two are different? They look identical to me.

[Tratcher]

The response in this case should not have been compressable. It was also inconsistent and appeared to be timing related. The other issue was consistent and related to compression.

[Tratcher]

Frequently reproduces with: ...
Reproduces less frequently with: ...

Umm... Am I not seeing how these two are different? They look identical to me.

await vs return. This can affect the timing.

[shapeh]

Hi, I was wondering if there are any news on this one?