-
Notifications
You must be signed in to change notification settings - Fork 10k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge Kestrel 2.2 #4031
Merge Kestrel 2.2 #4031
Conversation
- Making progress towards being able to use the connection objects on the client side.
[auto-updated: dependencies]
* Allow app to drain request buffer after FIN
[auto-updated: dependencies]
# Conflicts: # build/dependencies.props # korebuild-lock.txt # src/Kestrel.Transport.Libuv/Internal/LibuvConnectionContext.cs
This reverts commit 8e9f05b.
This reverts commit fe9da3c.
* Relieve response backpressure immediately when closing socket
[auto-updated: dependencies]
- Move ProcessRequest into ParseHttpRequest (out of state machine) - Use struct adapter for parsing - Non-virtual calls - RequestType to enum - Readonly statics and early init statics - Early init path statics - Faster Json fall through - CountingBufferWriter -> Smaller BufferWriter - Pre-init date static - Smaller WriteNumeric
- fix an issue with tests running as root on VSTS
Prior to this, only the response body counted toward the HTTP/2 response data rate. This PR aligns the HTTP/2 logic closer to the HTTP/1.x logic and measures the rate for all HTTP/2 response data. This PR also accounts for all response bytes written, not just those that immediately induced backpressure.
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.
The _streams dictionary may not contain the completing stream in OnStreamCompleted since the IsDraining flag is applied beforehand which allows it to be removed by the request processing thread.
Prior to this change, HTTP/2 read rate limit tests would fail when the stalled read started after the test started advancing the clock.
Prior to reorganization, this source code was found in https://github.com/aspnet/CodeGenerator/tree/15ba5065a9b220f545eb3118d9e552f0b7e824d0
…or Kestrel packages
…estrel test projects have the test logger installed
This reverts commit 0029b8f.
Prior to reorganization, this source code was found in https://github.com/aspnet/KestrelHttpServer/tree/4598850c20047554d59b08e3d1edab47c2d7fe69
554c436
to
9c48b1a
Compare
<Package Id="Microsoft.AspNetCore.DataProtection.Abstractions" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection.AzureKeyVault" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection.AzureStorage" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection.EntityFrameworkCore" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection.Extensions" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection.StackExchangeRedis" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection.SystemWeb" Version="2.2.0" /> | ||
<Package Id="Microsoft.AspNetCore.DataProtection" Version="2.2.0" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What changed in the sorting rules such that the base package is now last?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was manually sorting before and ran the sort lines command in VS Code. As it gets longer, manually sorting will be a pain
e0095a1
to
0271428
Compare
This merges release/2.1 and aspnet/KestrelHttpServer release/2.2.