Discussion: Why HTTP2 pseudo headers such as :authory are removed from Metadata about grpc-node

[murgatroid99]

First, some good news: there is work in progress to make the contents of the :authority header available to server interceptors (see grpc/proposal#433), and I can probably extend that to the call objects that the handlers get. The :path header uniquely determines what handler is called, so you can infer that from in the handler, and that information is also passed to server interceptors.

As for the reasoning, I would say that it mainly comes from the gRPC over HTTP2 protocol spec. Specifically, the "Custom-Metadata" production rule describes the request and response headers that are defined by the application, as opposed to headers defined and handled by the library. That is what the Metadata class in this library is supposed to correspond to.

[murgatroid99]

In version 1.11.x, server call objects have a getHost method, which returns the contents of the :authority header. They also already had the getPath method, which returns the contents of the :path header.