Skip to content

Document MultipartContent zero-part serialization behavior #12014

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.

Sign up for GitHub

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

Merged
merged 6 commits into from
Nov 6, 2025
Merged

Document MultipartContent zero-part serialization behavior #12014

Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
d5aff91
Initial plan
Copilot Nov 4, 2025
7a239c8
Document MultipartContent zero-part serialization behavior
Copilot Nov 4, 2025
068437d
Remove trailing whitespace from documentation
Copilot Nov 4, 2025
7bdeb66
Remove extra space before closing format tag
Copilot Nov 4, 2025
fe5447f
Apply suggestion from @MihaZupan
MihaZupan Nov 4, 2025
45fc75f
Update xml/System.Net.Http/MultipartContent.xml
MihaZupan Nov 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion xml/System.Net.Http/MultipartContent.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,14 @@
</Attributes>
<Docs>
<summary>Provides a collection of <see cref="T:System.Net.Http.HttpContent" /> objects that get serialized using the multipart/* content type specification.</summary>
<remarks>To be added.</remarks>
<remarks>
<format type="text/markdown"><![CDATA[
## Remarks
According to RFC 1341 (MIME) 7.2 and its successors, multipart messages must contain one or more body parts. When a <xref:System.Net.Http.MultipartContent> instance with zero parts is serialized, it's written as a single dummy empty part with no content headers or message body. This ensures compliance with the RFC requirement while maintaining backward compatibility. However, other HTTP clients might not interpret this message as a multipart content with zero parts, so it's recommended to add at least one part before serializing.
]]></format>
</remarks>
</Docs>
<Members>
<MemberGroup MemberName=".ctor">
Expand Down