Skip to content

Commit 285b300

Browse files
handrewsralfhandl
andcommitted
Name the right section matching the link (review feedback)
🤦 thanks for catching this, @ralfhandl Co-authored-by: Ralf Handl <[email protected]>
1 parent 65c2960 commit 285b300

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

versions/3.0.4.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1695,7 +1695,7 @@ This makes the presence of at least one of `style`, `explode`, or `allowReserved
16951695
###### Encoding `multipart` Media Types
16961696

16971697
The `form-data` disposition and its `name` parameter are mandatory for `multipart/form-data` ([RFC7578 §4.2](https://www.rfc-editor.org/rfc/rfc7578.html#section-4.2)).
1698-
Array properties are handled by applying the same `name` to multiple parts, as is recommended by [RFC7578 §4.2](https://www.rfc-editor.org/rfc/rfc7578.html#section-4.3) for supplying multiple values per form field.
1698+
Array properties are handled by applying the same `name` to multiple parts, as is recommended by [RFC7578 §4.3](https://www.rfc-editor.org/rfc/rfc7578.html#section-4.3) for supplying multiple values per form field.
16991699
See [RFC7578 §5](https://www.rfc-editor.org/rfc/rfc7578.html#section-5) for guidance regarding non-ASCII part names.
17001700

17011701
Various other `multipart` types, most notable `multipart/mixed` ([RFC2046 §5.1.3](https://www.rfc-editor.org/rfc/rfc2046.html#section-5.1.3)) neither require nor forbid specific `Content-Disposition` values, which means care must be taken to ensure that any values used are supported by all relevant software.

0 commit comments

Comments
 (0)