Solved: http2 support in Apigee x 2025

abhijithsh

I am checking on how to enable http2 in Apigee since our target system supports it and ALPN negotiation too.

1. Does Apigee handle http protocol negotiation automatically ?

2. It was recommended to use grpc target server to enforce http2 requests. Is it not possible to just use the http protocol with ssl ? Why is Apigee not negotiating and calling http2 is target supports it ?

3. If I have to use grpc target server, will it support falling back to http1.1 if the target server does not support it.

@dchiesa1 @API-Evangelist

a_aleinikov

Hi @abhijithsh ,

Apigee X does not support HTTP/2 to the target server by default. It accepts HTTP/2 from clients, but outbound to the target is usually HTTP/1.1.
ALPN negotiation is not used for automatic HTTP/2 upgrade on target connections. That’s why using just HTTPS with a target that supports HTTP/2 doesn’t result in HTTP/2 being used.
gRPC target servers enforce HTTP/2, even if you’re not using gRPC. However, they do not fall back to HTTP/1.1 — the target must support HTTP/2.

View solution in original post

a_aleinikov

Hi @abhijithsh ,

Apigee X does not support HTTP/2 to the target server by default. It accepts HTTP/2 from clients, but outbound to the target is usually HTTP/1.1.
ALPN negotiation is not used for automatic HTTP/2 upgrade on target connections. That’s why using just HTTPS with a target that supports HTTP/2 doesn’t result in HTTP/2 being used.
gRPC target servers enforce HTTP/2, even if you’re not using gRPC. However, they do not fall back to HTTP/1.1 — the target must support HTTP/2.

abhijithsh

Thanks for your answer. Is there any way to enable http2 when calling target server except using grpc so that we can have a fallback to http1.1 if the http2 is not enabled by the target server.