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
In grpcio==1.62.0 a regression (#33935, #35323) was fixed which caused rpcs to fail if the server responds with a content-type other than application/grpc.
For instance, GCP Identity Aware Proxy responds with 401 and content-type text/html to unauthenitcated requests, even if the request headers contain accept=application/grpc.
This issue is a follow up to the ones mentioned above:
With grpcio>=1.62.0, rpcs don't fail anymore but the status code is not correctly mapped:
Calling a minimal greeter service behind GCP Identity Aware Proxy without including any Authorization header ultimately results in grpc-status: 2/StatusCode.UNKNOWN even though the debug logs (and also the load balancer logs) show that the server responds with 401 which is initially also correctly mapped to grpc-status: 16 (UNAUTHENTICATED).
As a user of the grpc client library, I would expect the resulting status code to be grpc-status: 16/StatusCode.UNAUTHENTICATED in this case.
In
grpcio==1.62.0
a regression (#33935, #35323) was fixed which caused rpcs to fail if the server responds with a content-type other thanapplication/grpc
.For instance, GCP Identity Aware Proxy responds with 401 and content-type
text/html
to unauthenitcated requests, even if the request headers containaccept=application/grpc
.This issue is a follow up to the ones mentioned above:
With
grpcio>=1.62.0
, rpcs don't fail anymore but the status code is not correctly mapped:Calling a minimal greeter service behind GCP Identity Aware Proxy without including any Authorization header ultimately results in
grpc-status: 2
/StatusCode.UNKNOWN
even though the debug logs (and also the load balancer logs) show that the server responds with 401 which is initially also correctly mapped togrpc-status: 16
(UNAUTHENTICATED).As a user of the grpc client library, I would expect the resulting status code to be
grpc-status: 16
/StatusCode.UNAUTHENTICATED
in this case.The text was updated successfully, but these errors were encountered: