Skip to content
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

Merged
merged 11 commits into from
Apr 15, 2022
Merged

Conversation

dougbu
Copy link
Member

@dougbu dougbu commented Apr 15, 2022

dougbu and others added 11 commits April 27, 2021 22:37
- 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
@dougbu dougbu changed the title Dougbu/merge/v3.2.8 Merge tag 'v3.2.8' into 'main' Apr 15, 2022
Comment on lines +323 to +326
if (string.Equals("expires", name, StringComparison.OrdinalIgnoreCase))
{
ignoreHeaderValidation = true;
}
Copy link
Member Author

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 #263 and #313

@@ -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);
Copy link
Member Author

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
Copy link
Member Author

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

Comment on lines -11 to -12
<requireLicenseAcceptance>true</requireLicenseAcceptance>
<licenseUrl>http://www.microsoft.com/web/webpi/eula/mvc4extensions_prerelease_eula.htm</licenseUrl>
Copy link
Member Author

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.
Copy link
Member Author

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).

@dougbu dougbu merged commit 646f452 into aspnet:main Apr 15, 2022
@dougbu dougbu deleted the dougbu/merge/v3.2.8 branch April 15, 2022 01:35
dougbu added a commit to dougbu/AspNetWebStack that referenced this pull request Apr 15, 2022
- redo merge to restore the complete history
- I accidentally squashed in aspnet#319 / 646f452
dougbu added a commit that referenced this pull request Apr 15, 2022
- redo merge to restore the complete history
- no files changed because I accidentally squashed the commits in #319
@dougbu dougbu added this to the 3.2.9 milestone Feb 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants