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
This is a feature request/question. Does the interceptor support HTTP2 incoming connections? It seems like the net/http package should support this but when I
use curl with --http2 requests come back as http1.1, seemingly indicating that keda didn't respond saying it supports it
use curl with force http2, the requests fail due to "msg":"Not Found","routingKey":"///*/", even though in my request I am setting the host and even the authority headers.
Use-Case
HTTP2 has a lot of useful properties and I would like to use it to improve connection pooling done by downstream clients to our keda service.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Proposal
This is a feature request/question. Does the interceptor support HTTP2 incoming connections? It seems like the
net/http
package should support this but when I--http2
requests come back as http1.1, seemingly indicating that keda didn't respond saying it supports it"msg":"Not Found","routingKey":"///*/"
, even though in my request I am setting thehost
and even theauthority
headers.Use-Case
HTTP2 has a lot of useful properties and I would like to use it to improve connection pooling done by downstream clients to our keda service.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered: