The connection semantics for the result.
Close the connection once the response body has been sent.
This will take precedence to any Connection header specified in the request.
No buffering of the response will be attempted. This means if the result contains no Content-Length header,
none will be calculated.
Prefer to keep the connection alive.
If no Content-Length header is present, and no Transfer-Encoding header is present, then the body will be
buffered for a maximum of one chunk from the enumerator, in an attempt to calculate the content length. If the
enumerator contains more than one chunk, then the body will be sent chunked if the client is using HTTP 1.1,
or the body will be sent as is, but the connection will be closed after the body is sent.
There are cases where the connection won't be kept alive. These are as follows:
- The protocol the client is using is HTTP 1.0 and the client hasn't sent a Connection: keep-alive header.
- The client has sent a Connection: close header.
- There is no Content-Length or Transfer-Encoding header present, the enumerator contains more than one chunk,
and the protocol the client is using is HTTP 1.0, hence chunked encoding can't be used as a fallback.