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
{{ message }}
This repository has been archived by the owner on Dec 1, 2024. It is now read-only.
Currently, the incoming traffic can be HTTP/2 or HTTP/1.1 configurable but the outgoing traffic is hard-coded to HTTP/2 only. So far, we are OK as all of our downstream services are built on top of light-4j which support HTTP2 natively. When using the light-router with other downstream services, we need to provide an option to support HTTP/1.1 in the configuration.
The text was updated successfully, but these errors were encountered:
Currently, the incoming traffic can be HTTP/2 or HTTP/1.1 configurable but the outgoing traffic is hard-coded to HTTP/2 only. So far, we are OK as all of our downstream services are built on top of light-4j which support HTTP2 natively. When using the light-router with other downstream services, we need to provide an option to support HTTP/1.1 in the configuration.
The text was updated successfully, but these errors were encountered: