# Proxy authentication (Elxir reverse proxy performance)

**URL:** <https://forum.elixirforum.com/t/proxy-authentication-elxir-reverse-proxy-performance/28574>\
**Category:** Questions\
**Tags:** performance\
**Created:** [January 25, 2020, 5:34pm UTC](https://forum.elixirforum.com/t/proxy-authentication-elxir-reverse-proxy-performance/28574 "2020-01-25T17:34:49Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ityonemo](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/ityonemo/32/11341_2.png) [@ityonemo](https://forum.elixirforum.com/u/ityonemo)\
**Post date:** [January 28, 2020, 3:18am UTC](https://forum.elixirforum.com/t/proxy-authentication-elxir-reverse-proxy-performance/28574/7 "2020-01-28T03:18:25Z")

</div>

Definitely listening to this space. There’s a place in my deployment where I’ll need to proxy a one-way encrypted https inbound connection to a two-way encrypted https connection. I can do this with nginx but I’m a little bit scared about reloading nginx configs when I need to dynamically add a new route, (Maybe that’s silly). I know it should be possible in elixir, but am curious as to why or why not use the BEAM as a reverse proxy.

---

_[View the full topic](https://forum.elixirforum.com/t/proxy-authentication-elxir-reverse-proxy-performance/28574)._
