-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How many CONNECT UDP requests per QUIC connection? #114
Comments
It is OK to create multiple connect-udp requests on the same connection |
Maybe say so somewhere in the draft? |
There's no such language for vanilla CONNECT UDP, what does this document change? |
I am looking at management issues, and "how many connections can a client establish through the proxy" is indeed a problem. Resource is not infinite. What is the proxy to do when there are too many Connect UDP contexts open? Yes, there should be something like that in Connect UDP. But there isn't. |
Why should there be something in connect-udp? The issue of limiting the number of requests per connection is general to HTTP and in no way specific to connect-udp or to this extension. Servers can use flow control stream limits to choose exactly how many requests they want to allow. |
Agreed |
I think the same question of limits would apply to normal CONNECT/CONNECT-TCP in general. While something might be worth saying here, I don't think it's in this document alone? |
Do we request that a client establishes a new QUIC/H3 connection to the proxy for each target, or is it OK to simply create multiple proxy connections by sending multiple CONNECT-UDP requests on the same connection?
The text was updated successfully, but these errors were encountered: