Istio can automatically detect HTTP and HTTP/2 traffic. If the protocol cannot automatically be determined, traffic will be treated as plain TCP traffic.
Protocol selection:
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/
`Istio can automatically detect HTTP and HTTP/2 traffic. If the protocol cannot automatically be determined, traffic will be treated as plain TCP traffic.`
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#http-gateway-protocol-selection
ofilter
added this to the Istio-base project 2023-04-23 23:14:18 +02:00
ofilter
changed title from HTTP version to HTTP2 gateway2023-04-24 06:15:58 +02:00
Welp couldn't manage so will set it at the bottom of priorities and move on to other things.
Noticed that by setting the name of the port from the service object, as "http2", it did send HTTP2 traffic (according to logs generated), BUT:
client sent invalid request while reading client request line, client: 127.0.0.6, server: lb.net, request: "PRI * HTTP/2.0"
No idea how to handle this.
Welp couldn't manage so will set it at the bottom of priorities and move on to other things.
Noticed that by setting the name of the port from the service object, as "http2", it did send HTTP2 traffic (according to logs generated), BUT:
```txt
client sent invalid request while reading client request line, client: 127.0.0.6, server: lb.net, request: "PRI * HTTP/2.0"
```
No idea how to handle this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Protocol selection:
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/
Istio can automatically detect HTTP and HTTP/2 traffic. If the protocol cannot automatically be determined, traffic will be treated as plain TCP traffic.https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#http-gateway-protocol-selection
HTTP versionto HTTP2 gatewayMaybe I switch from HTTP2 gateway to HTTP2 backend, as noticed that once I have HTTPS, the traffic automatically gets set to HTTP2
HTTP2 gatewayto HTTP2 backendWelp couldn't manage so will set it at the bottom of priorities and move on to other things.
Noticed that by setting the name of the port from the service object, as "http2", it did send HTTP2 traffic (according to logs generated), BUT:
No idea how to handle this.