@miconda I don't think it is needed to modify any of the flags except the one
controlling multiplexing.
@grumvalski I had a quick look at the http_client module, and don't think it is
affected by this issue. It uses curl_easy_perform(), which is a blocking call.
--
You are receiving this becau
@grumvalski I think the fix in your branch is good enough! It is the
multiplexing that is the problem, not http2.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2632#issuecommen
We have now tested
https://github.com/kamailio/kamailio/tree/grumvalski/disable_http2_multiplexing
and it seems to solve our problems!
@miconda I would ague that this is a better solution than disabling TLS ALPN.
Now we can continue use http2, which is a more efficient protocol than http
1.1,
I nicer solution would be to fully implement support for http2!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2632#issuecomment-803385884__
I can confirm that patching http_async_client module by adding
`curl_easy_setopt(cell->easy, CURLOPT_SSL_ENABLE_ALPN, 0L);` solved our
problems. Now we don't see any spinning Kamailio processes anymore.
--
You are receiving this because you are subscribed to this thread.
Reply to this email dir
We suspect that the issue only happens with http2. @amessina I can see that the
server you connect to is also using http2. Looking at the implementation of
http_async_client it doesn't seem to handle http2 properly.
If you understood the implementation correctly these is an association between
We see the same issue on both 5.3 and 5.4:
```
version: kamailio 5.3.8 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE,
USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC,
DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE
