default envoy config fails silenlty with custom metadata

[supermihi]

Resolving this issue just cost me a few hours: with the example envoy config, all metadata keys except custom-header-1 cause envoy to drop the request. This is very hard to track down, especially because envoy, even with debug output enabled, does not make clear that the disallowed header is the problem.

In my case, I am using a custom authorization scheme that employs the recommended authorization header. Perhaps it would make sense to include at least that theader in the sample config?

[GregYeo]

If we consider grpc-web is replacement of REST client, That would be great because grpc-web is running on Browser and many REST API expects to use Authorization header and it is natural usage pattern.

I don't see any problem it causes when the header is allowed.

[sampajano]

Hi! The request makes sense! We can certainly include authorization header in our sample config. 😃