Baoyuantop commented on issue #13002: URL: https://github.com/apache/apisix/issues/13002#issuecomment-3956299895
Hi @singhajitk, thank you for your detailed report and for clarifying that you are looking for gateway-to-upstream HTTP/2 support. I'd like to clarify the current behavior. The `scheme: https` setting in the `ApisixUpstream` resource is designed to enable TLS encryption for the connection to the upstream service. It does not, by itself, alter the application-layer protocol, which defaults to HTTP/1.1 for standard proxying. This is why you are observing HTTP/1.1 being used. Your observation that setting the scheme to `grpcs` enables HTTP/2 is interesting. This happens because the `grpcs` scheme forces APISIX to configure the connection for gRPC, which inherently uses HTTP/2. While this may appear to work with a non-gRPC backend that supports HTTP/2 over TLS, it is an unintended side effect and not a supported configuration for standard HTTP services. Relying on this could lead to unexpected behavior as it bypasses logic intended for regular HTTP traffic. True support for HTTP/2 to a generic HTTPS upstream is currently not available as a direct feature. We recognize this as a valuable enhancement. We will treat this as a feature request to add a dedicated option to enable HTTP/2 for upstream connections explicitly, perhaps through a new field in the `ApisixUpstream` spec. We appreciate you bringing this to our attention. Please feel free to follow the issue for updates, and we welcome any contributions from the community to help implement this feature. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
