You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 30, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: versions/3.0.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1466,7 +1466,7 @@ When passing complex objects in the `x-www-form-urlencoded` content type, the de
1466
1466
1467
1467
It is common to use `multipart/form-data` as a `Content-Type` when transferring request bodies to operations. In contrast to 2.0, a `schema` is required to define the input parameters to the operation when using `multipart` content. This allows complex structures as well as supports mechanisms for multiple file uploads.
1468
1468
1469
-
When passing in `multipart` types, boundaries MAY be used to separate sections of the content being transferred--thus, the following default `Content-Type`s are defined for `multipart/*`:
1469
+
When passing in `multipart` types, boundaries MAY be used to separate sections of the content being transferred — thus, the following default `Content-Type`s are defined for `multipart/*`:
1470
1470
1471
1471
* If the property is a primitive, or an array of primitive values, the default Content-Type is `text/plain`
1472
1472
* If the property is complex, or an array of complex values, the default Content-Type is `application/json`
0 commit comments