aspnetcore

Author	SHA1	Message	Date
Nikita Tsukanov	39951e892e	Don't throw in HttpRequestStream.Flush (#2342 ) Because read-only streams apparently can have Flush semantics and this behavior is expected by some of built-in stream wrappers (e. g. CryptoStream) https://github.com/dotnet/corefx/pull/27327#pullrequestreview-98384813 https://github.com/aspnet/KestrelHttpServer/issues/2341	2018-02-23 09:51:09 -08:00
David Fowler	3fc69dc71f	Updated Streams to override Memory and Span overloads (#2333 ) - Also plumbed Memory/Span through Kestrel over ArraySegment. - Throw synchronously from the HttpRequestStream instead of async in some cases.	2018-02-21 00:00:46 -08:00
Pranav K	186e9806cd	Update samples and tests to target netcoreapp2.1	2017-11-16 14:43:15 -08:00
Cesar Blum Silveira	a31d1e024c	Merge code paths duplicated between HTTP/1.x and HTTP/2 implementations (#2017 ). - Most of the shared code is in the HttpProtocol class (former Frame) - Virtual calls handle protocol-specific things - Move the ProcessRequestsAsync loop to HttpProtocol - Implement HTTP/1.x request processing in Http1Connection and HTTP/2 in Http2Stream, with Http1Connection<T> and Http2Stream<T> subclassing those classes in order to handle the generic HttpContext parameter - Split MessageBody into Http1MessageBody and Http2MessageBody, with MessageBody containing shared member variables and methods	2017-09-14 17:35:57 -07:00