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
Are there any guides or knowledge regarding support of the new QUIC / HTTP/3-Protocol-Stack?
From what I know about QUIC this should improve transferspeed ?
Is there a way to make use of QUIC with some kind of QUIC-Proxy to tunnel tus/tcp ?
Thanks for your help
--mirac
Setup details
Please provide following details, if applicable to your situation:
Operating System: OpenBSD
Used tusd version: n/a
Used tusd data storage: disk store
Used tusd configuration: TLS-cert and key-file
Used tus client library: Uppy.js
The text was updated successfully, but these errors were encountered:
I just tested Caddy as reverse-proxy in front of tusd. Works great without any tweaking.
Looks like Google Chrome connects over UDP (according to tcpdump output on the server) and Safari doesn't due to lack of QUIC support.
So I tested upload-speed with Safari and Chrome but it was almost the same speed.
Maybe my Wifi or anything below Layer 4 is the bottleneck here...
tusd does not support QUIC connections natively because the net/http package from Go only supports up to HTTP/2. So running QUIC traffic through a proxy is necessary for now. However, I cannot help you much with missing speed improvements, as I have no practical experience with QUIC.
Question
Are there any guides or knowledge regarding support of the new QUIC / HTTP/3-Protocol-Stack?
From what I know about QUIC this should improve transferspeed ?
Is there a way to make use of QUIC with some kind of QUIC-Proxy to tunnel tus/tcp ?
Thanks for your help
--mirac
Setup details
Please provide following details, if applicable to your situation:
The text was updated successfully, but these errors were encountered: