Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove/disable manual response chunking
See original GitHub issueIf the application specifies a Transfer-Encoding: chunked response header then kestrel takes that as a signal that the app has implemented its own chunking and so the server should not auto-chunk. It’s not clear that this feature has ever been used as intended, but it does keep breaking apps that are forwarding responses from HttpClient.
Proposal: Disable and or remove this feature. Consider adding an option or quirk to re-enable it just in case anybody was using it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Triage: We initially thought this was a Kestrel specific behavior that was both inconsistent and annoying. However, we’ve now realized that it’s implemented consistently across IIS, HttpSys, and Kestrel, and the IIS behavior is out of our control. While it remains annoying, we’ve decided to leave it here because at least it’s consistent.
Ah, here’s the wiki I was looking for. https://github.com/dotnet/aspnetcore/wiki/Quirks-mode-switches-in-patches