Content-Length not set on outbound response

[cgatian]

When WebpackMiddleware.cs modifies the response stream content to inject a script tag the content length is not set to the new length of the response. This causes the HTTP response to get cutoff prematurely.

Content length should be updated to memStream.length the when copying to the new stream.

[xabikos]

Thanks for the input @cgatian

I tried to change the code and set the content length after copying the stream but I got an exception that SetContentLength method is not implemented in FrameResponseStream class.

Then I am not sure that this is the problem. Because I turned off the webpack middleware and in the response there is no Content-Length header too.

Could you provide an example that demonstrates the problem?

[cgatian]

All you need to do is set response.Headers.content length = stream.length

[xabikos]

How are you sure that this is the problem? I am just asking as I see that Kestel by default doesn't set this header. Maybe I am mistaken but if this was the problem then the server by default would have set this header for all html requests.

[cgatian]

That makes sense.
I cloned the repo and stepped though it. Setting the header ended up fixing it, but maybe there's something else I'm missing.

[xabikos]

Ok I will implement that change then and push a new version in nuget as soon as possible then. Thanks for catching that.

[xabikos]

I just pushed version 1.2.4
Please let me know if you have any other issues or ideas on improving the package