Skip to content

client transport: ignore HTTP/2 status if content-type is application/grpc #8486

@dfawley

Description

@dfawley

The gRPC spec does not indicate that we should be validating the HTTP/2 status if the content-type is set correctly as a gRPC status. This is to allow us to translate gRPC errors to HTTP statuses on the server side. Go should follow this behavior.

Metadata

Metadata

Assignees

Labels

Area: TransportIncludes HTTP/2 client/server and HTTP server handler transports and advanced transport features.P2Type: Bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions