# Local httpadmin access from http request node

**URL:** <https://discourse.nodered.org/t/local-httpadmin-access-from-http-request-node/84983>\
**Category:** General\
**Created:** [28 January 2024 09:49 UTC](https://discourse.nodered.org/t/local-httpadmin-access-from-http-request-node/84983 "2024-01-28T09:49:30Z")\
**Posts on this page:** 3\
**Page:** 3

<div class="post-metadata">

**Author:** ![helander](https://avatars.discourse-cdn.com/v4/letter/h/65b543/32.png) [@helander](https://discourse.nodered.org/u/helander)\
**Post date:** [3 February 2024 16:38 UTC](https://discourse.nodered.org/t/local-httpadmin-access-from-http-request-node/84983/41 "2024-02-03T16:38:05Z")

</div>

I fail to understand why the use of the node-red flows in combinationt with the node-red editor is an anti-pattern. From my point of view, Node-Red is an excellent rapid prototyping environment. Using Inject nodes or similar to trigger a chain of events is very simple, and as I see it where node-red shines in comparison with other environments.  
Web applications that interact with a node-red backend, is one of many ways to design a system, but it is far from main stream.

Most of my node-red deployments have no specific UI requirements, and having to create a web application is just a lot of work for no value.

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [4 February 2024 21:15 UTC](https://discourse.nodered.org/t/local-httpadmin-access-from-http-request-node/84983/42 "2024-02-04T21:15:51Z")

</div>

I completely agree that node-red is the best rapid-prototyping system I've used, and the most fun! The anti-pattern comment was mostly tongue-in-cheek, since we keep hearing about how the node-red editor is NOT meant to be a "dashboard". In reality, many of us (including me) do use it exactly for the purposes you are describing.

I disagree that surrounding your flows with http in/out nodes is a lot of work, or out of the main stream. They provide a very simple, targeted way to allow non-admin users to trigger parts of my flows without direct access to the entire editor. No web application needed for the end users, just a browser and a url.

And since you were specifically looking for a way to write a generic flow that makes an http request back to the same node-red server, without hardcoding the host:port/path info -- having the `msg.req` properties would certainly add value to your flows. Anyway, if you do find a more generic way to call back to the same server, please post your solution here for the rest of us. Best of luck...  
\_\_  
Steve

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [4 May 2024 21:16 UTC](https://discourse.nodered.org/t/local-httpadmin-access-from-http-request-node/84983/43 "2024-05-04T21:16:48Z")

</div>

Closed on 4 May 2024 21:16 UTC

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

[Previous page](https://discourse.nodered.org/t/local-httpadmin-access-from-http-request-node/84983.md?page=2)
