# Http3 support?

**URL:** <https://meta.discourse.org/t/http3-support/329153>\
**Category:** Feature\
**Tags:** docker\
**Created:** [October 3, 2024, 8:53am UTC](https://meta.discourse.org/t/http3-support/329153 "2024-10-03T08:53:50Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![fredrikj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fredrikj/32/453112_2.png) [@fredrikj](https://meta.discourse.org/u/fredrikj)\
**Post date:** [October 4, 2024, 5:50pm UTC](https://meta.discourse.org/t/http3-support/329153/16 "2024-10-04T17:50:09Z")

</div>

Another approach would be to add, to the docker image, a dedicated HTTP reverse proxy to handle HTTP3 traffic and only that. E.g, you could embedd say [Envoy Proxy](https://www.envoyproxy.io/) - which supports HTTP3 ingress - and configure it to listen only on port 443/udp for h3 traffic, and transform all incoming h3 requests to h2 or h1.1 and forward to the Nginx instance.

A bit of a hack though, so won’t say it’s a good idea. 🙂

---

_[View the full topic](https://meta.discourse.org/t/http3-support/329153)._