Closed kazu-yamamoto closed 1 year ago
Thanks for the heads up! I haven't migrated to http2-tls
yet, still using my own integration. It's on my list of things to do :)
Found it :) Thanks for the heads up.
The problem is that by the time you have TLS the sockets are well hidden inside backend closures... Could these be Maybe, so they are optional?
We don't plan to move to http-tls as we do custom CA verification and there is another use case for a more precise control of TLS sessions... For now migrated to 4.1.4, but looking at some addressed vulnerability recently it would be great to move to the latest...
If SockAddr
is not available, please specify a dummy one (e.g. SockAddrInet 0 0
).
yep, that's what I ended iup doing :)
Testing 4.2.2 now
It fixed the problem with the exception in streaming not getting to the call! 🚀
Hopefully it'll fix some of the file sending errors we have
Great!
My project (DNS over HTTP/2) requires to log a pair of socket addresses.
This provides my
SockAddr
and peer'sSockAddr
throughAux
toServer
.Config
has breaking changes. Ifhttp2-tls
is used, these changes are not visible.Cc: @edsko @epoberezkin