gRPC-Gateway

Fixed an issue where the plugin mapped the gRPC UNIMPLEMENTED status to HTTP 500 instead of 501. The new option use_standard_grpc_status_codes (default off) enables the fix.

Fixed an issue where a single query-parameter value for a repeated integer or enum field failed to transcode, so such values are now correctly mapped to the gRPC request.

Fixed an issue where the plugin mapped the gRPC UNIMPLEMENTED status to HTTP 500 instead of 501. The new option use_standard_grpc_status_codes (default off) enables the fix.

Fixed a bug where the TE (transfer-encoding) header would not be sent to the upstream gRPC servers when grpc-web or grpc-gateweay are in use.

Fixed a bug where the TE (transfer-encoding) header would not be sent to the upstream gRPC servers when grpc-web or grpc-gateweay are in use.

When there is a JSON decoding error, respond with status 400 and error information in the body instead of status 500.

Fixed an issue where an array with one element would fail to be encoded.

Fixed an issue where empty (all default value) messages couldn’t be unframed correctly.#10836

Fixed an issue where having a null value in the JSON payload caused an uncaught exception to be thrown during pb.encode.#10687

Fixed an issue where empty arrays in JSON were incorrectly encoded as "{}". They are now encoded as "[]" to comply with standards.#10790

Added the missing protocols field to the following plugin schemas: gRPC Gateway (grpc-gateway)

Fixed the handling of boolean fields from URI arguments.#9180

Added the missing protocols field to the following plugin schemas: gRPC Gateway (grpc-gateway)