如何向gRPC-JSON Transcoder端点提交REST请求及排障

Let's break down how to fix your REST request issues and debug the Envoy configuration step by step.

First: Fix the REST Request Format #

Your grpcurl call works, so the Envoy transcoder is partially configured correctly—but your curl commands have common mistakes. Let's start with the right request syntax:

Case 1: No HTTP Annotations in Your Proto #

If your helloworld.proto doesn't include google.api.http bindings, the transcoder uses the default gRPC service/method path. You must use a POST request (since GET can't carry a JSON body) with the full service+method path:

curl \
  --request POST \
  --header "Content-Type: application/json" \
  --data '{"name":"Freddie"}' \
  http://0.0.0.0:51051/helloworld.Greeter/SayHello

Your first curl attempt used GET with a body—this is invalid HTTP and will fail immediately.

Case 2: With HTTP Annotations in Your Proto #

If you added REST bindings to your proto (like below), adjust your curl to match the defined paths:

service Greeter {
  rpc SayHello (HelloRequest) returns (HelloReply) {
    option (google.api.http) = {
      get: "/say"  // GET with query param
      additional_bindings {
        post: "/say"  // POST with JSON body
        body: "*"
      }
    };
  }
}

• For GET:

  curl \
    --request GET \
    http://0.0.0.0:51051/say?name=Freddie
  

• For POST:

  curl \
    --request POST \
    --header "Content-Type: application/json" \
    --data '{"name":"Freddie"}' \
    http://0.0.0.0:51051/say
  

Debugging Envoy Configuration & Upstream Issues #

The error upstream connect error or disconnect/reset before headers. reset reason: remote reset points to either a misconfigured transcoder or a failure to reach your gRPC service on :50051. Here's how to dig deeper:

1. Enable Detailed Envoy Logs #

Envoy's default logs are too quiet—enable debug-level logging to see exactly what's failing. Update your Envoy config to add:

admin:
  access_log_path: /tmp/admin_access.log
  address:
    socket_address: { address: 0.0.0.0, port_value: 9901 }
static_resources:
  listeners:
    - name: listener_0
      address: { socket_address: { address: 0.0.0.0, port_value: 51051 } }
      filter_chains:
        - filters:
            - name: envoy.filters.network.http_connection_manager
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
                access_log:
                  - name: envoy.access_loggers.file
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
                      path: /tmp/envoy_access.log
                log_level: debug  # Critical for debugging
                # ... rest of your HTTP manager config

After restarting Envoy, check /tmp/envoy_access.log—it will show details like:

• Did Envoy recognize the REST path and map it to the correct gRPC method?
• Is Envoy failing to connect to the upstream :50051 service?

2. Validate Transcoder Configuration via Admin Console #

Visit http://0.0.0.0:9901/config_dump in your browser or use curl to fetch the config. Look for the grpc_json_transcoder filter section and verify:

• proto_files or proto_descriptor includes your helloworld.proto and all dependencies (like google/api/http.proto if you used annotations).
• services explicitly lists helloworld.Greeter (if you set it—omitting this can cause the transcoder to ignore the service).
• grpc_service points correctly to your upstream gRPC service (e.g., a cluster pointing to :50051).

3. Test Upstream Reachability from Envoy #

If Envoy is running in a container or separate host, confirm it can actually reach the gRPC service on :50051:

• Exec into the Envoy container (if applicable): docker exec -it <envoy-container> /bin/sh
• Run grpcurl directly from Envoy to the upstream:

  grpcurl \
    --plaintext \
    --import-path=${HELLOWORLD} \
    --import-path=${GOOGLEAPIS} \
    --proto=helloworld/helloworld.proto \
    -d '{"name":"Test"}' \
    <gRPC-service-host>:50051 \
    helloworld.Greeter/SayHello
  

If this fails, the problem is network connectivity between Envoy and your gRPC service—not the transcoder itself.

4. Check for Missing Proto Dependencies #

If you used google.api.http annotations in your proto, you must ensure Envoy has access to google/api/http.proto and google/api/annotations.proto. If these are missing from your import_paths in the transcoder config, the transcoder can't parse the REST bindings, leading to silent failures.

Final Checks #

• Double-check the Content-Type header is exactly application/json—any typo (like application/json; charset=utf-8) can cause the transcoder to reject the request.
• Ensure your gRPC service is running and listening on :50051 (use netstat -plnt or ss -plnt to verify).

内容的提问来源于stack exchange，提问作者DazWilkin