# Looking to add https node responses

**URL:** <https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279>\
**Category:** Dashboard\
**Tags:** function-node\
**Created:** [26 March 2025 21:01 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279 "2025-03-26T21:01:02Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [26 March 2025 21:01 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/1 "2025-03-26T21:01:02Z")

</div>

Looks like "node-red-contrib-http" has been deprecated. Searching Library I found "node-red-contrib-http-request" but haven't tried that one. Looking for recommendation

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [26 March 2025 21:24 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/2 "2025-03-26T21:24:59Z")

</div>

Hi. Welcome to the forum.

Question: Why are you installing http nodes when node-red has http-request built in?

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [26 March 2025 21:31 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/3 "2025-03-26T21:31:02Z")

</div>

https is what I'm looking for. Trying to give responses to a webhook server that requires https

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [26 March 2025 21:33 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/4 "2025-03-26T21:33:26Z")

</div>

To clarify. You are creating an endpoint in node-red that an external application calls?

Or the other way around (node-red calls an external application)

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [26 March 2025 21:38 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/5 "2025-03-26T21:38:16Z")

</div>

Yes, external cloud host sending status updates messages that I will point at my node-red install. Should be able to string match and trigger something else. I don't control the host side and it requires https for sending events.

BTW: I have configured certificates and https is working for dashboard access.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [26 March 2025 21:49 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/6 "2025-03-26T21:49:34Z")

</div>

Ok, well the 2 nodes you have mentioned were for making http(s) requests from node-red.

Regarding securing node-red, how do you access the node-red editor (via `http://xxx` or `https://xxx`)

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [26 March 2025 21:56 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/7 "2025-03-26T21:56:07Z")

</div>

https, used Certbot ACME client to generate the keys. That part is working!

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [26 March 2025 21:59 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/8 "2025-03-26T21:59:18Z")

</div>

Then you are all set. just create your endpoint using the built-in http-in -\> http-response nodes.

Cookbook: [Create an HTTP Endpoint : Node-RED](https://cookbook.nodered.org/http/create-an-http-endpoint)

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [26 March 2025 22:06 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/9 "2025-03-26T22:06:18Z")

</div>

I can't use the built in if the host is making https request...right? I was assuming I needed to install a different note capable of deciphering https request.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [26 March 2025 22:10 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/10 "2025-03-26T22:10:26Z")

</div>

If you access node-red via HTTPS then any endpoint you create using the http-in nodes will be accessible via HTTPS.

The http-in URL is relative to the editor.

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [26 March 2025 22:27 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/11 "2025-03-26T22:27:40Z")

</div>

GOOD to know... thank you!

---

<div class="post-metadata">

**Author:** ![kitori](https://avatars.discourse-cdn.com/v4/letter/k/f08c70/32.png) [@kitori](https://discourse.nodered.org/u/kitori)\
**Post date:** [27 March 2025 10:59 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/12 "2025-03-27T10:59:20Z")

</div>

I have a similar setup. here is my nginx config snippet with http basic auth:

```auto
 location /api/ {
        autoindex off;
        auth_basic "Auth for http-nodes";
        auth_basic_user_file /etc/apache2/.htpasswd;
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_pass http://127.0.0.1:1880/api;
}

```

in setting.js i set ` httpNodeRoot: '/api'`

so in the editor, i get:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/8/088b5fd2323cfc4717693c9dc3f00e9a015f0ab6.png)

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [27 March 2025 15:31 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/13 "2025-03-27T15:31:46Z")

</div>

That may be the clue I needed! I see the key is defining the API string. I was a bit confused how node-red would distinguish requests between dashboard access and node processing.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [27 March 2025 16:06 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/14 "2025-03-27T16:06:41Z")

</div>

> [@twincommander](#):
>
> I was a bit confused how node-red would distinguish requests between dashboard access and node processing.

you can add whatever you like in the URL field including...

- `/api/v1/my_endpoint`_(static route)_
- `/api/v1/my_endpoint/:param1/data/:param2`_(dynamic route)_
- `/fred/blogs/*`_(wildcard route)_

Any Parameters parsed from the URL will be available in `msg.params`

In short, you dont NEED to set `httpNodeRoot`

---

<div class="post-metadata">

**Author:** ![kitori](https://avatars.discourse-cdn.com/v4/letter/k/f08c70/32.png) [@kitori](https://discourse.nodered.org/u/kitori)\
**Post date:** [27 March 2025 18:24 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/15 "2025-03-27T18:24:40Z")

</div>

Yeah, but this setting prevent me doing dump Things after i forget what flow is doing after 1 year xD

I also set `httpAdminRoot: '/admin',`

---

<div class="post-metadata">

**Author:** ![twincommander](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/twincommander/32/99757_2.png) [@twincommander](https://discourse.nodered.org/u/twincommander)\
**Post date:** [8 April 2025 15:19 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/16 "2025-04-08T15:19:03Z")

</div>

For others who may read this.. The solution has been working great.

---

<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:** [22 April 2025 15:19 UTC](https://discourse.nodered.org/t/looking-to-add-https-node-responses/96279/17 "2025-04-22T15:19:30Z")

</div>

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