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
If we get some kind of an HTTP ERROR CODE from the grpc-web-proxy, currently the SDK is design to watch only for headers labeled: grpc-status and grpc-message and thus we cannot catch the empty headers with the empty response but with HTTP ERROR CODE errors, so we cannot mark this web-proxy as unhealthy.
Description
If we get some kind of an HTTP ERROR CODE from the grpc-web-proxy, currently the SDK is design to watch only for headers labeled:
grpc-status
andgrpc-message
and thus we cannot catch the empty headers with the empty response but with HTTP ERROR CODE errors, so we cannot mark this web-proxy as unhealthy.Steps to reproduce
Additional context
Here are the only two headers that we are currently watching:
https://github.com/hashgraph/hedera-sdk-js/blob/develop/src/channel/WebChannel.js#L71
Hedera network
mainnet, testnet, previewnet
Version
v2.19.1
Operating system
macOS
The text was updated successfully, but these errors were encountered: