Multipart form support

[KlausVcb]

Description

• Support for multipart/form-data Request Body returning the text key/value pairs as well as the files in the Request.
• Add extension method to read the form from a Request.
• Add extension method to read the body from a Request as a byte[]. Useful since the InputStream is a NetworkStream which might be receiving more data while already processing the body. Reading the body in a single Stream.Read usually works but not if the body is larger than a few kB.
• minor cleanup (rename file and removal of unused file)

Motivation and Context

• Multipart forms required manual parsing of the body beforehand.

How Has This Been Tested?

Unit tests have been added to cover the parsing of the multipart headers and a varia of entire forms as well.

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

Summary by CodeRabbit

• New Features
  • Introduced a new dependency for enhanced JSON handling capabilities.
• Bug Fixes
  • Improved project stability with the addition of the nanoFramework.Json library.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (11)

• README.md is excluded by !**/*.md and included by none
• nanoFramework.WebServer.FileSystem/nanoFramework.WebServer.FileSystem.nfproj is excluded by none and included by none
• nanoFramework.WebServer/HttpListenerRequestExtensions.cs is excluded by none and included by none
• nanoFramework.WebServer/HttpMultipartParser/HeaderUtility.cs is excluded by none and included by none
• nanoFramework.WebServer/HttpMultipartParser/LineBuffer.cs is excluded by none and included by none
• nanoFramework.WebServer/HttpMultipartParser/LineReader.cs is excluded by none and included by none
• nanoFramework.WebServer/HttpMultipartParser/MultipartFormDataParser.cs is excluded by none and included by none
• nanoFramework.WebServer/HttpMultipartParser/MultipartFormDataParserException.cs is excluded by none and included by none
• nanoFramework.WebServer/nanoFramework.WebServer.nfproj is excluded by none and included by none
• tests/nanoFramework.WebServer.Tests/HttpMultipartParser/FormDataProvider.cs is excluded by none and included by none
• tests/nanoFramework.WebServer.Tests/HttpMultipartParser/MultipartFormDataParserTests.cs is excluded by none and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request introduces a new direct dependency on nanoFramework.Json in the packages.lock.json file for the tests/nanoFramework.WebServer.Tests project. The requested and resolved version for this dependency is 2.2.152, and it includes a content hash for integrity verification. No other changes were made to the existing dependencies or the structure of the file.

Changes

File	Change Summary
tests/nanoFramework.WebServer.Tests/packages.lock.json	Added new direct dependency: "nanoFramework.Json": { "type": "Direct", "requested": "[2.2.152, 2.2.152]", "resolved": "2.2.152", "contentHash": "scImuHOxgKfsoX5i0QfOfpwzBLWFmXyGNN5ICSEO6e4GaVtiBJTWXhxNhwEP8T0MYdIyAJiEZLoIIHjAwm5A9A==" }

Possibly related PRs

• Update 3 NuGet dependencies #263: This PR updates the packages.lock.json file for tests/nanoFramework.WebServer.Tests, which includes changes to the same file as the main PR, specifically related to dependency version updates.
• Update 1 NuGet dependencies #275: This PR also modifies the packages.lock.json file for tests/nanoFramework.WebServer.Tests, updating the nanoFramework.TestFramework dependency, which is relevant to the context of dependency management in the same file.
• Update 1 NuGet dependencies #277: Similar to Update 1 NuGet dependencies #275, this PR updates the nanoFramework.TestFramework dependency in the packages.lock.json file for tests/nanoFramework.WebServer.Tests, indicating ongoing changes to dependencies in the same context.

Suggested labels

CI: Publish Release, Type: dependencies

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Ellerbach]

Thanks, nice addition! Couple of comments and remarks

[Ellerbach]

FEw more things, getting there! Thanks a lot

[KlausVcb]

I see the build didn't go through for the last change because of 'file in use'. Any way of retriggering it besides a dummy code change?

[Ellerbach]

I see the build didn't go through for the last change because of 'file in use'. Any way of retriggering it besides a dummy code change?

Done. Manually retriggerd

[KlausVcb]

Ok thanks. I see the build did pass #1.2.82+02921def11 but didn't update the PR checks.
So, anything left todo or are we good to merge?

[Ellerbach]

So, anything left todo or are we good to merge?

I just merged the latest update into the PR. As soon as the build is done, I'll go to merge it. Thanks again!

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Ellerbach]

Thanks again for this nice addition!