# Preventing timeout errors with the http request node

**URL:** <https://discourse.nodered.org/t/preventing-timeout-errors-with-the-http-request-node/50131>\
**Category:** General\
**Tags:** http-request\
**Created:** [24 August 2021 18:48 UTC](https://discourse.nodered.org/t/preventing-timeout-errors-with-the-http-request-node/50131 "2021-08-24T18:48:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisofCCL](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/chrisofccl/32/42442_2.png) [@chrisofCCL](https://discourse.nodered.org/u/chrisofCCL)\
**Post date:** [24 August 2021 18:48 UTC](https://discourse.nodered.org/t/preventing-timeout-errors-with-the-http-request-node/50131/1 "2021-08-24T18:48:44Z")

</div>

I have a flow that sometimes sends 'EVENTs' over http, using the http-request node. Events require no response, but of course the http-request node expects one. When one doesn't turn up within the timeout period, it generates a timeout error message, which I want to suppress. Is there any way to do that?

I am currently fudging the issue by sending a zero length string in response.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [25 August 2021 05:52 UTC](https://discourse.nodered.org/t/preventing-timeout-errors-with-the-http-request-node/50131/2 "2021-08-25T05:52:05Z")

</div>

The 'catch' node should produce events for this.

---

<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:** [24 October 2021 05:52 UTC](https://discourse.nodered.org/t/preventing-timeout-errors-with-the-http-request-node/50131/3 "2021-10-24T05:52:19Z")

</div>

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