Closed atacan closed 2 weeks ago
Hi @atacan,
yes this is expected, see OpenAPI 3.1.0:
In contrast with the 3.0 specification, the format keyword has no effect on the content-encoding of the schema. JSON Schema offers a contentEncoding keyword, which may be used to specify the Content-Encoding for the schema.
In 3.1.0, just change format: binary
to contentEncoding: binary
Thank you
Description
When a multipart request schema has a binary part
with
openapi: 3.0.0
we gethowever with
openapi: 3.1.0
we getThis throws the following error, when the server receives the request
error.type=Server error - cause description: 'User handler threw an error.', underlying error: Unexpected content type, expected: text/plain, received: application/octet-stream
Reproduction
Package version(s)
Expected behavior
binary file part should expect octet/stream instead of plain text.
Environment
Additional information
No response