-
Notifications
You must be signed in to change notification settings - Fork 74
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 for HTTP form encoded bodies #348
Comments
Supporting |
Is there an update on this? I'm having the same issue. Trying to get an HTTP call with a Content-Type = application/x-www-form-urlencoded to be transcoded to a post annotated gRPC call... The endpoint calling my gRPC service only supports this Content-Type, application/json is not possible. |
We don't have resource to work on this feature. We welcome community contribution. |
is this feature needed? try to clean up the issues. |
it is needed |
For many client applications such as oauth servers, it would be nice to have support for transcription of POST bodies in form encoding (https://www.w3.org/TR/html401/interact/forms.html#h-17.13.3.4), both application/x-www-form-urlencoded and multipart/form-data, to gRPC. This would work the same way as JSON transcoding, just from a different body encoding.
The text was updated successfully, but these errors were encountered: