gRPC

🐛 Bug Report

WithHealthzEndpoint didn't set Content-Type to anything but text/plain; charset=utf-8. Shouldn't it be application/json?

To Reproduce

1. Enable WithHealthzEndpoint
2. GET to the /healthz endpoint

Expected behavior

Content-Type: application/json
Grpc-Metadata-Content-Type: application/grpc

Actual Behavior

Content-Type: text/plain;

Allow to close tabs by hovering over a tab and clicking the middle mouse button.
Just like in web browsers. :)

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

Before you submit this issue, you has been search all existed issues and search the documentation

• [] I've been search all existed issues
• [] I've been read all documentation

Describe your question

How should I use alicloud MNS?

As we all know golang has give us the feature that convert proto to json with https://github.com/golang/protobuf/blob/master/jsonpb/encode.go ,and with encode.go ,we can define diffrent style like casesensitive , emit empty , json indent and so on , we can see [Customizing Protobuf JSON Serialization in Go](https://seb-nyberg.medi

Some users may want to add multiple query param values for a single key

e.g. localhost:8080/v1?id=1&id=2&id=3

However, WebClient.prepare().queryParam() performs a QueryParamsBuilder#setObject by default, making it
difficult to execute such a query programmatically

WebClient.prepare()
         .get("/")
         .queryParam("id", 1)
         .queryParam("id", 2)
         .q

Deprecated field: type envoy.config.bootstrap.v3.Admin Using deprecated option 'envoy.config.bootstrap.v3.Admin.access_log_path' from file bootstrap.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history for details. If continued use of this field is absolutely necessary, see https://www.envoyproxy.io/docs/e