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
At the moment, hface uses AnyIO UDPSocket (or any other UnreliableObjectStream[UDPPacketType]) for UDP transport. With this transport, every packet can be sent to a different address. CONNECT-UDP is not compatible with this approach because we need to specify a destination address at the connection time.
It can be best to switch to ConnectedUDPSocket (or more generally UnreliableObjectStream[bytes]):
I don't think that clients need to supports servers migrating between IP addresses.
Servers already use QUICListenerStream for routing packets and this class has a remote_address attributes.
This could help to get rid of some hacks that we use when we need remote_address for HTTP/3 connections.
HTTP/3 proxies can support CONNECT-UDP for proxying UDP packets. This can be used to proxy QUIC and HTTP/3 through HTTP/3 proxies.
ProxyClientSession.connect_udp()
and use it for proxying of HTTP/3 traffic.ProxyServer
.The text was updated successfully, but these errors were encountered: