Releases: Http-Multipart-Data-Parser/HttpMultipartParser
Releases · Http-Multipart-Data-Parser/HttpMultipartParser
6.0.0
As part of this release we had 2 issues closed.
Breaking Change
- #105 Drop support for outdated frameworks (net461, net472 and netstandard2.0)
Enhancement
- #108 Add comparison option to GetParametersValue(s)
5.1.0
As part of this release we had 2 issues closed.
Enhancements
- #100 Target net5.0
- #104 Argument Null Exception on Parse/ ParseAsync
5.0.1
As part of this release we had 1 issue closed.
Bug
- #98 "Search" method in "SubsequenceFinder" class have bug.
5.0.0
Please see this post for tips on how to upgrade from previous release to 5.0.0.
As part of this release we had 24 commits which resulted in 5 issues being closed.
Breaking Changes
- #95 Use optional parameter and reduce overloads
- #94 Remove obsolete MultipartFormDataParser constructors
- #88 Properties in the FilePart and ParameterPart classes should be read-only
- #85 Pass dictionary to FileHandler
Improvement
- #93 Maintain an IMultipartFormDataParser interface
4.4.0
As part of this release we had 22 commits which resulted in 2 issues being closed.
Improvements
- #91 Discontinue using BenchmarkDotNet dotnet tool
- #90 Files without filename are not recognized
4.3.1
As part of this release we had 4 commits which resulted in 1 issue being closed.
Bug
- #84 Null reference exception when handling file without a filename
4.3.0
As part of this release we had 12 commits which resulted in 1 issue being closed.
Improvement
- #83 "Key not found" exception when name and filename parameters are omitted
4.2.0
As part of this release we had 8 commits which resulted in 1 issue being closed.
Bug
- #33 OutOfMemoryException when form is empty
4.1.0
As part of this release we had 15 commits which resulted in 1 issue being closed.
Improvement
- #58 Exception with no parameter name is found
4.0.0
As part of this release we had 18 commits which resulted in 1 issue being closed.
Breaking Change
- #81 Allow multiple files with the same name