You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When throwing a ConnectError with special metadata fields on the (connect-fastify) server, the metadata fields are not part of the headers anymore in the client with grpc transport.
I tried to fix the bug by myself but give up at the end. My last guess was, that the metadata fields are dropped/overridden or not correctly converted to the http header. The fastify plugin code did not receive the error http headers.
Describe the bug
When throwing a
ConnectError
with specialmetadata
fields on the (connect-fastify
) server, the metadata fields are not part of the headers anymore in the client with grpc transport.I tried to fix the bug by myself but give up at the end. My last guess was, that the metadata fields are dropped/overridden or not correctly converted to the http header. The fastify plugin code did not receive the error http headers.
To Reproduce
I created a reproducible project: https://github.com/bobaaaaa/connect-fastify-bug
Environment:
Additional context
❤
The text was updated successfully, but these errors were encountered: