-
Notifications
You must be signed in to change notification settings - Fork 32
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
[question] unable to do request http2: unsupported scheme #13
Comments
Do you have any more information on Postman directly supporting http/2? I'm using Postman (7.27.1) on MacOS and it doesn't appear to support http/2 yet. Separately, can you export your Postman request as a Curl command and post it here? You may be missing a header in Postman to signal the proxy to modify the request. The log line above the one you posted may have additional relevant information. |
@jnewmano Sorry it took me a while to respond. I did follow the instructions from README to run docker container and proxy a request to it, this would be the cURL command: This would be the output of the proxy container: There's really nothing extra going on, just wanted to have basics up and running. As for http/2, seems like it really is not supported yet by Postman, but then I'm puzzled what responds to me with that message. 🤔 I'll appreciate any help. |
I also has the same issue. |
Greetings,
This is just a question, not a "request" for a solution.
I followed the guidelines to setup Postman (7.26.0) proxy and ran docker grpc-json-proxy, when trying to send a simple message I get this error:
2020/07/01 10:43:11 unable to do request err=[Post http://localhost:50051/notes.NoteService/List: http2: unsupported scheme]
I was wondering if the http/2 support is not implemented in your library or gRPC calls would generally not work over http/2 carrier?
It seems like you were writing that documentation before Postman defaulted to http/2 requests with no ability to specify protocol version for the requests.
Thank you
The text was updated successfully, but these errors were encountered: