In order to figure this out, it's recommended to open a support ticket so we can get some more detailed information.
Azure Api Management Self Hosted Gateway HTTP2 issue
Hello, I am trying to connect the APIM to the regular (non-web) Grpc .Net backend using a self-hosted gateway, however, I see in the APIM logs that the HTTP version is downgraded from 2.0 to 1.1 when communicating with the backend.
APIM is the Premium tier. I have a self-hosted gateway (v2.6.0) deployed to the Kubernetes with the default configuration parameters. Http 2.0 is enabled in protocols.
Grpc APIM API is created with the following backend policy.
<backend>
<forward-request http-version="2" />
</backend>
Communication with the backend is done through HTTPS. However, in APIM Logs I see that the protocol is downgraded when communicating with the backend and because of this (I assume) I don't receive trailing headers, which leads to "No grpc-status found on response." error. Please advise what am I doing wrong here.
1 answer
Sort by: Most helpful
-
Tom Kerkhove 0 Reputation points Microsoft Employee
2025-02-28T12:10:17.0166667+00:00