# HTTP Server Stop

## Overview

![The HTTP Server Stop Node.](/files/Bt24k1GpUnmP6ddxD4Dl)

The **HTTP Server Stop Node** terminates the connection with an **HTTP Server**.

It is important to note that while the **HTTP Server Stop Node** stops the connection to an **HTTP Server**, it may not completely finish disconnecting from said server when the **Node** is executed. This could lead to the **Logic** attached to its **Output Pulse** to not work even though there is technically nothing wrong. In order to avoid this, it is highly suggested to use the [**On HTTP Server Stop Node**](/incari-studio/toolbox/communication/http/events/onhttpserverstop.md) instead. This way, it is assured that the **Logic** will execute once the connection to the **HTTP** **Server** has been terminated.

Again, the user must first use the **HTTP Server Stop Node** to close the connection. Separately, the **On HTTP Server Stop Node** can be used to execute the desired **Communication Logic**.

![HTTP Server Stop and On HTTP Server Stop Configuration.](/files/PuUpFzHEKdiSYHxWBLPL)

[**Scope**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2025.1/toolbox/communication/overview.md#scopes): **Project**, **Scene**.

## Attributes

![The HTTP Server Stop Node Attributes.](/files/QuJ8eZKgeFIAndl1Ta3o)

| Attribute       | Type          | Description                                                                                                                                                         |
| --------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Configuration` | **Drop-down** | The desired *HTTP(S)* server, which refers back to the selections made under *HTTP* in the [**Project Settings**](/incari-studio/modules/project-settings/http.md). |

## Inputs

| Input             | Type      | Description                                                           |
| ----------------- | --------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**. |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## See Also

* [**HTTP Server Start**](/incari-studio/toolbox/communication/http/httpserverstart.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.incari.com/incari-studio/toolbox/communication/http/httpserverstop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.