During our evaluation of various HTTP/3 server solutions, we began exploring WebTransport as a potential option. However, we observed that server-side support for WebTransport does not appear to be available in NGINX at this time.
Approach Taken:
To investigate further, we developed a proof of concept by patching the open-source NGINX project to enable basic WebTransport functionality. While we were able to successfully handle a single stream, this implementation was limited in scope and not suitable for production use.
Request:
We would like to inquire whether there are any plans to officially support WebTransport in NGINX in the future. This capability would be highly valuable for our use cases, and we believe it could benefit the broader community as well.
We currently do not have near term plan to support it but plans change. I am curious to hear about your use case here and why do you think its the right approach for you?
We’ve been exploring the advantages of HTTP/3 to establish a standardized two-way communication channel, with the goal of potentially replacing our current WebSocket-based solution.
abusing webrtc to make udp-like connection between client and server, instead of peer to peer between the clients, is usually the approach when trying to make a voice/video conferencing apps. also any kind of unreliable client-server communication, meaninng that we tolerate data loss but cant tolerate latency, is impossible to do with websocket and have to rely on, again, webrtc which is super duper complex to set up. webtransport solves this.