Bridge filters are only used on unary gRPC. How about highlighting this?

[eottabom]

Title: Bridge filters are only used on unary gRPC. How about highlighting this?

Description:

Bridge filters are only used in unary gRPC. right?

However, many people send clients as http1.1(rest) requests and try to communicate with gRPC using those filters. As if, expect the operation of the gRPC-JSON Transcoder.

Therefore, I think the description of the filters should be emphasized.

Because, it's explained first as below.

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_http1_bridge_filter.html

This is a simple filter which enables the bridging of an HTTP/1.1 client which does not support response trailers to a compliant gRPC server

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_http1_reverse_bridge_filter.html

This is a filter that enables converting an incoming gRPC request into a HTTP/1.1 request to allow a server that does not understand HTTP/2 or HTTP/3 or gRPC semantics to handle the request

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.