YvCeung opened a new issue, #7712: URL: https://github.com/apache/incubator-seata/issues/7712
### Check Ahead - [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. - [x] I am willing to try to fix this bug myself. ### Ⅰ. Issue Description 当前 TC 与客户端的 HTTP 交互是非 HTTPS 请求，而现有的 OkHttp 工具类封装并不支持在这种场景下使用 HTTP/2，请求实际上仍会自动降级为 HTTP/1.1。 Currently, the HTTP interactions between TC and the client are over non-HTTPS requests. The existing OkHttp utility wrapper does not support using HTTP/2 in this scenario, and the requests are effectively downgraded to HTTP/1.1. ### Ⅱ. Describe what happened 当我在本地启动tc后，使用curl命令表名是可以支持http2请求的，但是当我使用http2的工具类发起调用，发现最终是http1的协议，本质并没有生效 When I start TC locally, using the curl command clearly supports HTTP/2 requests. However, when I use the HTTP/2 utility class to make the call, the requests ultimately fall back to HTTP/1, so HTTP/2 is not actually in effect. **curl:** <img width="821" height="132" alt="Image" src="https://github.com/user-attachments/assets/656e60cd-3c7c-4b84-8775-66c92420e0f4"; /> **util call:** <img width="1512" height="945" alt="Image" src="https://github.com/user-attachments/assets/2ad541e2-6079-4027-8074-27df2944113b"; /> <img width="1512" height="945" alt="Image" src="https://github.com/user-attachments/assets/6c3ac6e7-2e8c-4427-a15e-9287f2427de6"; /> ### Ⅲ. Describe what you expected to happen _No response_ ### Ⅳ. How to reproduce it (as minimally and precisely as possible) _No response_ ### Ⅴ. Anything else we need to know? _No response_ ### Ⅵ. Environment _No response_ -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
