Multipart handling not in-spec with Jakarta RESTful Web Services 3.1 using jakarta.ws.rs.FormParam #41148
Replies: 2 comments
-
I see we used the old resteasy 'classic', and the question is wrong- quarkus seems to handle it correctly. When updating to using |
Beta Was this translation helpful? Give feedback.
0 replies
-
This should probably be reopened. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As far as I understand,
multipart/form-data
is not actually implemented according to the spec in regards to@jakarta.ws.rs.FormParam
. The spec clearly states that the following should be valid:In the provided example, we have the following resource:
Which in Quarkus doesn't work. I have attached a minimal example where it doesn't work. Using the following test-command, we see that the part always get set to null. This is true no matter the type of
part
;String
, which the docs say should work also doesn't.curl -vvv -F "part1=hello" http://localhost:8080/api/upload
Is there a good reason why
@FormParam
support is not a feature and instead replaced using@RestForm
in resteasy-reactive? I would like to report this as an issue but I assume some thought has been put into this.Beta Was this translation helpful? Give feedback.
All reactions