Since version 1.10.9 grpc-node doesnt comply with grpc spec in case of non 200 response

[RemiBou]

Problem description

When server returns HTTP 404 with "404 not found" in body grpc-node throws a RESOURCE_EXHAUSTED

Reproduction steps

Init your grpc client with a non grpc server, it should throw "UNIMPLEMENTED" error, instead it might throw "RESOURCE_EXHAUSTED"

Environment

• grpcnode >= 1.10.9

Additional context

I think it's same issue as #2809
I want to add that this should be fixed in grpc-node as it doesn't comply with the grpc spec anymore. Reference
https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md

Implementations should expect broken deployments to send non-200 HTTP status codes in responses as well as a variety of non-GRPC content-types and to omit Status & Status-Message. Implementations must synthesize a Status & Status-Message to propagate to the application layer when this occurs.

When "404" is return by server then grpc status 12 and error UNIMPLEMENTED should be send to the client application.

Java and GO grpc library work that way and grpc-node used to work that way until this commit 674f4e3

[murgatroid99]

OK, I see the problem: the RESOURCE_EXHAUSTED error from attempting to parse the response body is superseding the UNIMPLEMENTED error from the HTTP status.

[RemiBou]

@murgatroid99 do you think it should be fixed ?

[murgatroid99]

Nothing has happened with this yet.