fix #2240 HTTP 400 error with vertx-web-openapi backend and Swagger UI #2241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation:
According to a discussion in the OpenAPI specification github repo (discussion including Mike Ralphson, a major OpenAPI contributor), it seems that:
*/*
is an acceptable value*/*
:OAI/OpenAPI-Specification#1692 (comment)
But it is true that, when omitted in the spec, the
application/octet-stream
mime type is implied (and this precisely what Vert.x is doing):https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.1.md#special-considerations-for-multipart-content
Supporting the
*/*
content type will allow writing upload forms that will accept any type of file sent by Swagger UI.