aspnetcore/test/Kestrel.FunctionalTests
David Fowler 7854c0604a Remove the events on ConnectionContext (#2023)
- Use the pipe events and removed the Tasks from ConnectionContext
- Remove OnConnectionClosed from FrameConnection. Since the `FrameConnetion` is a single middleware, not the entire pipeline, we shouldn't need to wait on the connection close there.
- It seems like the callbacks are rooted on the pipe even after they fire. This needs to be investigated in pipelines.
2017-08-26 20:19:55 -07:00
..
Properties
…
SystemdActivation
…
TestHelpers
…
AddressRegistrationTests.cs Use PackageLineup 2017-08-16 14:10:43 -07:00
BadHttpRequestTests.cs
…
ChunkedRequestTests.cs
…
ChunkedResponseTests.cs
…
ConnectionAdapterTests.cs
…
ConnectionLimitTests.cs
…
DefaultHeaderTests.cs
…
EventSourceTests.cs Stop using ConcurrentBag in tests for complex types (#1990) 2017-08-11 16:30:03 -07:00
FrameConnectionManagerTests.cs
…
GeneratedCodeTests.cs Initial HTTP/2 support. 2017-08-16 10:04:44 -07:00
HttpsConnectionAdapterTests.cs Add fixes for problems discovered by xunit.analyzers (#1999) 2017-08-16 09:37:49 -07:00
HttpsTests.cs
…
KeepAliveTimeoutTests.cs
…
Kestrel.FunctionalTests.csproj Use PackageLineup 2017-08-16 14:10:43 -07:00
ListenHandleTests.cs
…
LoggingConnectionAdapterTests.cs
…
MaxRequestBodySizeTests.cs
…
MaxRequestBufferSizeTests.cs
…
MaxRequestLineSizeTests.cs
…
RequestBodyTimeoutTests.cs
…
RequestHeaderLimitsTests.cs
…
RequestHeadersTimeoutTests.cs
…
RequestTargetProcessingTests.cs
…
RequestTests.cs Remove the events on ConnectionContext (#2023) 2017-08-26 20:19:55 -07:00
ResponseTests.cs Fix flakiness in ConnectionClosedWhenResponseDoesNotSatisfyMinimumDataRate (#1955). 2017-08-24 10:17:05 -07:00
ThreadCountTests.cs
…
UpgradeTests.cs
…