aspnetcore/test/Kestrel.InMemory.Functional...
Stephen Halter f2a383dc76
Don't count long tick intervals against rate measurements (#3070)
This might help address #3015

This only affects rate timeouts. Normal fixed timeouts might deserve the same treatment, but that would require some additional locking to ensure we don't modify the sentinel value.
2018-11-02 10:58:30 -07:00
..
Http2 Don't count long tick intervals against rate measurements (#3070) 2018-11-02 10:58:30 -07:00
Properties
TestTransport
BadHttpRequestTests.cs
CertificateLoaderTests.cs
ChunkedRequestTests.cs
ChunkedResponseTests.cs
ConnectionAdapterTests.cs
ConnectionLimitTests.cs
DefaultHeaderTests.cs
EventSourceTests.cs
HttpConnectionManagerTests.cs
HttpProtocolSelectionTests.cs
HttpsConnectionAdapterTests.cs
HttpsTests.cs Add interop tests with headless chrome 2018-10-25 10:38:41 -07:00
KeepAliveTimeoutTests.cs
Kestrel.InMemory.FunctionalTests.csproj
LoggingConnectionAdapterTests.cs Add interop tests with headless chrome 2018-10-25 10:38:41 -07:00
MaxRequestBodySizeTests.cs
MaxRequestLineSizeTests.cs
RequestBodyTimeoutTests.cs Don't count long tick intervals against rate measurements (#3070) 2018-11-02 10:58:30 -07:00
RequestHeaderLimitsTests.cs
RequestHeadersTimeoutTests.cs Measure the rate of all HTTP/2 output (#3067) 2018-10-31 15:34:17 -07:00
RequestTargetProcessingTests.cs
RequestTests.cs Fix test flakiness caused by not reading in a loop (#3023) 2018-10-16 18:15:46 -07:00
ResponseDrainingTests.cs Don't count long tick intervals against rate measurements (#3070) 2018-11-02 10:58:30 -07:00
ResponseTests.cs
UpgradeTests.cs