Skip to content

Commit

Permalink
Name the right section matching the link (review feedback)
Browse files Browse the repository at this point in the history
🤦 thanks for catching this, @ralfhandl

Co-authored-by: Ralf Handl <[email protected]>
  • Loading branch information
handrews and ralfhandl authored Jun 11, 2024
1 parent a4f3498 commit f1f745c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion versions/3.0.4.md
Original file line number Diff line number Diff line change
Expand Up @@ -1670,7 +1670,7 @@ This makes the presence of at least one of `style`, `explode`, or `allowReserved
###### Encoding `multipart` Media Types

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)).
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.
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.
See [RFC7578 §5](https://www.rfc-editor.org/rfc/rfc7578.html#section-5) for guidance regarding non-ASCII part names.

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.
Expand Down

0 comments on commit f1f745c

Please sign in to comment.