Making firefox quic capable by running a forwardproxy on the same machine - downsides?


I’m running a Caddy webserver with QUIC support and want to make Firefox capable to communicate with this server over QUIC.

Firefox doesn’t yet support QUIC. So my idea is to setup a quic reverse proxy on the same machine where Firefox runs. The overhead to communicate via TCP to the reverse proxy should be negligible because it uses a loopback device.

My only goal is to connect to THIS webserver. I’m not interested in general quic connections to youtube or something like that. So the static caddy file is fine for me.

I’ve tested it and it seems to work well. But I’ve never seen a similar setup. Could you tell me if there any downside in this setup?


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.