-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MultipartBody uploads with declarative HTTP client #722
Comments
The sample application includes a test with the standard HTTP client and that test passes but with a warning. I don't know if I'm guilty or if the framework does something wrong. Maybe it's related to issue #721
|
I created issue #726 for the |
@goeh You have to set the correct content type. The test passes with |
@goeh I noticed that the same warning occurs when the declarative client is used. This is a different issue than 726 and I'm going to push the fix soon |
@jameskleeh I just added produces = "...." and you are correct, it works. That's awesome, thanks! |
@goeh Perhaps it could, I'm not sure. If you think the docs could be made more clear please submit a PR. |
Upload MultipartBody with declarative HTTP @client seems to be unsupported. It would be nice if it was.
Steps to Reproduce
Expected Behaviour
A multipart request should be sent to the destination
Actual Behaviour
Environment Information
Example Application
The text was updated successfully, but these errors were encountered: