-
Notifications
You must be signed in to change notification settings - Fork 353
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 tag 'v3.2.8' into 'main' #319
Conversation
dougbu
commented
Apr 15, 2022
- see https://github.com/aspnet/AspNetWebStack/releases/tag/v3.2.8 for prominent issues resolved as well as a more detailed list of changes
- reformat README.md - merge 'Git tag' and 'Git branch' columns - remove old v3.2.4 / v5.2.4 information - add v3.2.7 / v5.2.7 information
- test using netcoreapp2.1 - react to .NET Core breaking change - see https://docs.microsoft.com/en-us/dotnet/core/compatibility/2.1#path-apis-dont-throw-an-exception-for-invalid-characters - suppress NU5125 warnings - break the build because warnings are treated as errors - do not validate Expires header values - aspnet#263
Constrain the MemoryStream size
aspnet#312) * Configure max request line size limits to be the same as maxHeaderSize As part of ReadAsHttpRequestMessageAsync, the parsing of the HTTP request line is limited by a non-configurable 2k limit. The size does not affect buffer sizes, only the maximum allowed length. This PR updates the ReadAsHttpRequestMessageAsync API to use the same limits for HTTP request line as the HTTP header line, the latter which is configurable by user code. In the default case, this means the HTTP request line size now supports a 16k limit before it throws. Fixes aspnet#307
- remove `<requireLicenseAcceptance/>` as well - can't require a license w/o `<license/>` or `<licenseUrl/>` - also, don't need to ignore NU5125 anymore
- brings in recent fixes from last release
if (string.Equals("expires", name, StringComparison.OrdinalIgnoreCase)) | ||
{ | ||
ignoreHeaderValidation = true; | ||
} |
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.
@@ -223,7 +223,7 @@ public static Task<HttpRequestMessage> ReadAsHttpRequestMessageAsync(this HttpCo | |||
|
|||
HttpUnsortedRequest httpRequest = new HttpUnsortedRequest(); | |||
HttpRequestHeaderParser parser = new HttpRequestHeaderParser(httpRequest, | |||
HttpRequestHeaderParser.DefaultMaxRequestLineSize, maxHeaderSize); | |||
Math.Max(HttpRequestHeaderParser.DefaultMaxRequestLineSize, maxHeaderSize), maxHeaderSize); |
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.
This is the fix for #307
/// has become available allowing the action to write to it directly. When the | ||
/// stream is closed, it will signal to the content that is has completed and the | ||
/// has become available allowing the action to write to it directly. When the | ||
/// stream is closed, it will signal to the content that it has completed and the |
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.
Doc comment updates in this class
are to fix #310
<requireLicenseAcceptance>true</requireLicenseAcceptance> | ||
<licenseUrl>http://www.microsoft.com/web/webpi/eula/mvc4extensions_prerelease_eula.htm</licenseUrl> |
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.
The two changes like this are part of our fix for #314. The rest is in internal build infrastructure. Yes, we are working toward including YAML in this repo for the builds.
// Treat .NET Core 2.0 as a .NET 4.5 superset though internal types are different. | ||
// Treat .NET Core 2.1 as a .NET 4.5 superset though internal types are different. |
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.
.NET Core 2.0 is out of support. 2.1 is also mostly out of support but ASP.NET Core 2.1.x is still getting updates for many packages (those that work on full "desktop" .NET Framework).
- redo merge to restore the complete history - I accidentally squashed in aspnet#319 / 646f452
- redo merge to restore the complete history - no files changed because I accidentally squashed the commits in #319