# HTTP

## Introduction

The **HTTP Nodes** provide a means for the user to perform several actions within the *HTTP* protocol. *HTTP*, or *Hypertext Transfer Protocol*, allows for communication between servers and clients by way of requests and responses using different methods.

The **HTTP Nodes** allow the user to set up a server or connect to an already existing server. To set up a server on the local machine in **Incari**, the user needs to locate the [**HTTP Attributes**](/incari-studio/modules/project-settings/http.md) in **Project Settings** and add a server. To connect to an external server, the **HTTP Client Node** should be used.

**Incari** provides the possibility for establishing connections with both *HTTP* and *HTTPS* servers as well as setting up these two server types. *HTTPS* is an extension of the *HTTP* communication protocol which utilizes *SSL* encryption for security purposes.

## HTTP Guideline

With the **HTTP Communication Nodes**, except the **HTTP Client Node**, the user can create a server on the local machine. From there, they can process requests and send respective responses as desired. With the **HTTP Client Node**, the user can make any request to any server.

The following guideline shows the steps needed for setting up a server on a local machine.

* To properly start a connection, see the [**General Guideline**](/incari-studio/toolbox/communication.md#general-guideline) on the Communications Introduction page.
* Once the connection has been established, there are a couple of **Nodes** that cover important functions of **HTTP Communication**.
  * [**On HTTP Route**](/incari-studio/toolbox/communication/http/events/onhttproute.md) executes when an **HTTP Request** from a specified **Route** is received.
  * [**HTTP Response**](/incari-studio/toolbox/communication/http/httpresponse.md) defines a response for a particular request.
* To properly stop a connection, see the [**General Guideline**](/incari-studio/toolbox/communication.md#general-guideline) on the Communications Introduction page.

## Contents

* [**Events**](/incari-studio/toolbox/communication/http/events.md)
  * [**On HTTP Route**](/incari-studio/toolbox/communication/http/events/onhttproute.md)
  * [**On HTTP Server Start**](/incari-studio/toolbox/communication/http/events/onhttpserverstart.md)
  * [**On HTTP Server Stop**](/incari-studio/toolbox/communication/http/events/onhttpserverstop.md)
* [**HTTP Client**](/incari-studio/toolbox/communication/http/httpclient.md)
* [**HTTP Response**](/incari-studio/toolbox/communication/http/httpresponse.md)
* [**HTTP Server Start**](/incari-studio/toolbox/communication/http/httpserverstart.md)
* [**HTTP Server Stop**](/incari-studio/toolbox/communication/http/httpserverstop.md)

## External Links

* More information on [*HTTP*](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) on Wikipedia.
* More information on [*HTTPS*](https://en.wikipedia.org/wiki/HTTPS) on Wikipedia.


---

# 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.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.