Clarify response wire protocol details, buffering, chunked, content-length, etc.

[Tratcher]

When proxying behind IIS/Express there are a few un-expected side-effects. We need to at least document these, but also consider how to work around them if needed. See the affected tests in Universe\ServerTests\test\ServerComparison.FunctionalTests\ResponseTests.cs

1. Buffering vs streaming - what buffering is done by the platform handler or by default IIS scenarios? How can be enable full streaming?
2. Chunked vs Content-length - as a result of the default buffering, chunked responses are converted to content-length.
3. Connection: close - This only appears to close the connection between the proxy and the back-end server, it does not close the connection with the client.

[Tratcher]

@davidfowl

[muratg]

@Tratcher we can move out if needed.

[davidfowl]

@Tratcher Let's get a meeting with the http platform handler guys to go over this after we verify all of the behaviors.

[avanderhoorn]

Any chance anyone knows what the current buffer size is?

[Tratcher]

@avanderhoorn My testing shows the buffer is 8kb.

[avanderhoorn]

Huge thanks!

On Thursday, November 19, 2015, Chris R notifications@github.com wrote:

@avanderhoorn https://github.com/avanderhoorn My testing shows the
buffer is 8kb.

—
Reply to this email directly or view it on GitHub
#7 (comment)
.