# Use Node-RED as reverse proxy

**URL:** <https://discourse.nodered.org/t/use-node-red-as-reverse-proxy/13017>\
**Category:** General\
**Created:** [7 July 2019 23:17 UTC](https://discourse.nodered.org/t/use-node-red-as-reverse-proxy/13017 "2019-07-07T23:17:04Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [3 June 2020 21:33 UTC](https://discourse.nodered.org/t/use-node-red-as-reverse-proxy/13017/35 "2020-06-03T21:33:23Z")

</div>

> [@ristomatti](#):
>
> There's a caution note about this in the documentation

Thanks for your assistance!  
Indeed this node has been developed to solve a number of problems, but it is not a full blown http proxy:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/7/57e840eda2ea7ac3582e7cf3f7f4511de9852cc2.png)

> [@josekavunkal](#):
>
> .I can see the target url as browser URL .

Can you explain that more in detail please, because with so less information I can only start guessing. Because in the browser you use an url referring to your Node-RED server, not to the target url?

---

_[View the full topic](https://discourse.nodered.org/t/use-node-red-as-reverse-proxy/13017)._
