From 95bab7f8efabc4cbe56674307fb9ed258751e22d Mon Sep 17 00:00:00 2001 From: smhc Date: Thu, 2 Apr 2020 12:39:01 +1000 Subject: [PATCH] Update 3.0.3.md format is 'byte' not 'base64'. --- versions/3.0.3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versions/3.0.3.md b/versions/3.0.3.md index e21aa46554..b7c616d34d 100644 --- a/versions/3.0.3.md +++ b/versions/3.0.3.md @@ -1446,7 +1446,7 @@ In contrast with the 2.0 specification, `file` input/output content in OpenAPI i # content transferred with base64 encoding schema: type: string - format: base64 + format: byte ``` ```yaml @@ -1537,7 +1537,7 @@ When passing in `multipart` types, boundaries MAY be used to separate sections o * If the property is a primitive, or an array of primitive values, the default Content-Type is `text/plain` * If the property is complex, or an array of complex values, the default Content-Type is `application/json` -* If the property is a `type: string` with `format: binary` or `format: base64` (aka a file object), the default Content-Type is `application/octet-stream` +* If the property is a `type: string` with `format: binary` or `format: byte` (aka a file object), the default Content-Type is `application/octet-stream` Examples: