# HTTP ## Utility ### ASYNC Has Internet Check
{% hint style="info" %} ### ASYNC Has Internet Check ## Overview This utility checks whether the user's system is currently connected to the internet. It does this by performing a lightweight HTTP request to [**https://www.google.com**](https://www.google.com/). If the request is successful, the node returns **true** otherwise, it returns **false**. ## Inputs **None.** ## Outputs * **Success** – Executes If the user has a valid internet connection. * **False** – Executes If the user does not have a valid internet connection. * **Has Internet** – A Boolean output: **true** if the system is online, **false** otherwise. {% endhint %} *** ## ASYNC ### ASYNC HTTP(S) Request
{% hint style="info" %} ### ASYNC HTTP(S) Request ## Overview Send a **HTTP(S)** request to the specified URL using one of several supported request types. This node is useful for interacting with **RESTful APIs**, **web services**, or **cloud-hosted endpoints**. Automatically parses the response data into a **JSON** output. You can send requests with or without a body, specify the timeout, and receive detailed information back, including status code, content type, and response headers. Useful for game server communication, cloud saves, analytics, player profile data, etc. If you’re expecting a binary response, the node will automatically detect **binary-only** data and place it into the **Out Binary Data** output. **Note**: If the response contains binary content *inside a JSON structure*, it will still be delivered through **Out Json** as part of the parsed JSON payload.
## Supported Request Types * **GET**– Retrieves data from the server (**default**). * **POST** – Sends data to the server, typically for creating new resources. * **PUT** – Sends data to update/replace a resource. * **PATCH** – Partially updates an existing resource. * **DELETE** – Deletes a resource on the server. * **HEAD** – Retrieves headers only (no body). * **TRACE** – Echoes the received request (**used for diagnostics**). ## Inputs * **URL** – The full URL to send the request to. * **Request Type** – Select the HTTP verb from the supported types above. * **Timeout** – Duration (**in seconds**) to wait for a server response before failing. * [**Request Body**](https://doc.uforge.co.uk/structs#make-download-settings) – (**Optional**) JSON data or payload to send with the request (used with **POST**, **PUT**, **PATCH**). And header definition. ## Outputs * **On Success** – Triggered when a valid response is received. * **On Progress** – Fires as the request is actively processed. * **On Streamed** – Fires as chunked responses are recieved. **SSE** or **binary only** data. * **On Failed** – Triggered if the request fails. * **Out Json** – Parsed JSON response object. * **Out Binary Data** - If binary-only data is detected, it will be provided here for direct access. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. **Note:** If an error occurs during the HTTP request. Either from the server or within the node itself. An error message will be returned as a JSON response for you to handle in "**Out Json**". {% endhint %} *** ### ASYNC Download File
{% hint style="info" %} ### ASYNC Download File ## Overview Send a **HTTP(S)** **file download** request to a specified URL. This node can either return the raw **binary data** of the file or save the file directly to the user’s machine, depending on the **Download Settings** provided. ## Inputs * **URL** – The full **HTTP/HTTPS** address of the file to be downloaded. * **Timeout** – How long (**in seconds**) to wait before the request times out. * [**Download Settings**](https://doc.uforge.co.uk/structs#make-download-settings) – Optional structure to define how the downloaded file will be handled after download has finished, and header definition. ## Outputs * **On Success** – Executes when the file download completes successfully. * **On Progress** – Called as the download progresses. Useful for tracking progress percentage. * **On Failed** – Executes if the download fails. * **Download Percentage** – A float value between 0.0 and 100 representing the progress of the download. * **Response Code** – The response code from the server. * **Downloaded Binary Data** – The raw binary file data. Only available if file is not directly saved to disk. * **Response Headers** – An array of all headers returned by the server. {% endhint %} *** ### ASYNC Upload Multipart File
{% hint style="info" %} ### ASYNC Upload Multipart File ## Overview Send a **multipart/form-data upload request** to a specified URL. It allows uploading one or more binary files (**e.g. images, logs, audio, Videos**) to an external API using the **multipart/form-data** format. The request is fully customizable via **Upload Settings** and supports attaching extra headers and multipart fields. The server's response is parsed and returned as a **JSON** object. ## Inputs * **URL** – The target endpoint to send the file upload request to. * **Timeout** – How long (**in seconds**) to wait before the request times out. * [**Upload Settings**](https://doc.uforge.co.uk/structs#make-httprequest-settings) – A structure that defines how the request is configured, including custom headers and option to choose a random or defined boundary. * [**File Data**](https://doc.uforge.co.uk/structs#make-upload-file-data) – An array of file definitions. Each entry in this array represents a single file to be uploaded and includes all of its corresponding settings. Each file definition also supports its own individual **multipart form data**, allowing for precise control over how each file is handled in the request. ## Outputs * **On Success** – Triggered when the file upload is successfully completed and a valid response is received. * **On Progress** – Called as data is being uploaded. * **On Failed** – Triggered when the request fails. * **Out Json** – The parsed server response. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. **Note:** If an error occurs during the **Multipart upload request**. Either from the server or within the node itself. An error message will be returned as a JSON response for you to handle. {% endhint %} *** ### ASYNC Multipart Request
{% hint style="info" %} ### ASYNC Multipart Request ## Overview Send a **multipart/form-data HTTP request** to a specified URL. It's commonly used to transmit structured data in separate parts. Ideal for **form** submissions or **API payloads**. The multipart request is configured using the "**Multipart Data"** struct. Which allows full control over **headers**, boundaries. And last but not least the core Multipart data. ## Inputs * **URL** – The endpoint to which the multipart request is sent. * **Timeout** – How long (**in seconds**) to wait before the request times out. * [**Multipart Data**](https://doc.uforge.co.uk/structs#make-multipart-http-data) – Structured multipart data built using **Make Multipart HTTPData**. This includes parts (fields or files), optional custom headers, and multipart boundary configuration. ## Outputs * **On Success** – Triggered when the server responds with a successful HTTP code. * **On Progress** – Fires as data is being sent. * **On Failed** – Triggered when the request fails or times out. * **Out Json** – A parsed JSON object returned by the server. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. **Note:** If an error occurs during the **Multipart request**. Either from the server or within the node itself. An error message will be returned as a JSON response for you to handle. {% endhint %} *** ## Functions that are shared between non ASYNC HTTP(S) Nodes ### Add Headers To Request
{% hint style="info" %} ### Add Header To Request ## Overview This utility node adds one or more **HTTP headers** to an existing HTTP request object. Headers are used to provide more information about the request. Such as authorization tokens, content types, client identifiers, or custom metadata. This is essential when communicating with APIs that require specific headers for access or formatting. This node must be called before the request is sent. ## Inputs * **Target** – The **HTTP(S)** request object we want to set the headers for. The target node must be a child of class "**HTTPProxyBase**" * **New Headers** – A map of headers to be added. ## Outputs * **Success** – Returns **true** if the headers were successfully added to the request. Otherwise, returns **false.** {% endhint %} *** ### Remove Header From Request
{% hint style="info" %} ### Remove Header From Request ## Overview This utility node removes a specified **HTTP(S)** header from an existing **HTTP(S)** request object provided by the "**Target**" input pin. Individual Headers are removed by specifying their key name. This can be useful when modifying or removing a single header from the existing request. This node must be called before the request is sent. ## Inputs * **Target** – The **HTTP(S)** request object we want to remove the header for. The target node must be a child of class "**HTTPProxyBase**" * **Key** – The name of the HTTP header to remove. ## Outputs * **Success** – Returns **true** if the headers were successfully removed from the request. Otherwise, returns **false.** {% endhint %} *** ### Set New Timeout
{% hint style="info" %} ### Set New Timeout ## Overview This utility node overrides the current timeout duration for a specific **HTTP(S)** request. The timeout defines how long (**in seconds**) the request will wait for a server response before being considered failed. This is particularly useful for adjusting responsiveness in low-latency or slow-network scenarios. This node must be called before the request is sent. ## Inputs * **Target** – The **HTTP(S)** request object we want to set a new timeout for. The target node must be a child of class "**HTTPProxyBase**" * **New Timeout** – Timeout duration in **seconds**. ## Outputs None. {% endhint %} *** ### Set New URL
{% hint style="info" %} ### Set New URL ## Overview This node updates the **target URL** of an existing **HTTP(S)** request. It allows you to dynamically modify the endpoint address that the request will be sent to. Useful when when reusing request logic with variable endpoints or having a dynamic endpoint input. This node must be called before the request is sent. ## Inputs * **Target** – The **HTTP(S)** request object we want to set a new URL for. The target node must be a child of class "**HTTPProxyBase**" * **New URL** – A string representing the new destination URL. ## Outputs None. {% endhint %} *** ### Process HTTP Request
{% hint style="info" %} #### Process HTTP Request ## Overview This node finalizes and sends a constructed **HTTP(S)** request to its desired URL using the settings and data you've defined prior to sending the request. It is the final step in sending the request and must be called after all modifications (e.g., setting URL, headers, timeout) are complete. ## Inputs * **Target** – The **HTTP(S)** request object we want to set a new URL for. The target node must be a child of class "**HTTPProxyBase**" ## Outputs * **Success** – Returns **true** if the request was successfully sent to the endpoint. Otherwise returns **false.** {% endhint %} *** ### Cancel HTTP Request
{% hint style="info" %} ### Cancel HTTP Request ## Overview This node cancels an **in-progress HTTP(S) request** tied to a given request object. If the request is currently executing or pending, it will be immediately terminated and treated as failed. This is useful for cases where the result is no longer needed. ## Inputs * **Target** – The **HTTP(S)** request object we want to set a new URL for. The target node must be a child of class "**HTTPProxyBase**" ## Outputs * **Success** – Returns **true** if the request was successfully cancelled. Otherwise returns **false.** {% endhint %} *** ## Non ASNYC HTTP(S) Request ### Create New HTTP Request
{% hint style="info" %} ### Create New HTTP Request ## Overview This node mirrors the functionality of the [**ASYNC** version](#async-http-s-request) but creates a new **non-ASYNC** **HTTP(S)** request instance. Since it is **non-ASYNC**, the request does not need to be sent immediately after creation. The node outputs an "**HTTPProxy"** object, which can be manually configured and executed. It is typically used in scenarios where developers need direct control over request execution, progress tracking, and the ability to cancel the request. ## Supported Request Types * **GET**– Retrieves data from the server (**default**). * **POST** – Sends data to the server, typically for creating new resources. * **PUT** – Sends data to update/replace a resource. * **PATCH** – Partially updates an existing resource. * **DELETE** – Deletes a resource on the server. * **HEAD** – Retrieves headers only (no body). * **TRACE** – Echoes the received request (**used for diagnostics**). ## Inputs * **URL** – The full URL to send the request to. * **Request Type** – Select the HTTP verb from the supported types above. * **Timeout** – Duration (**in seconds**) to wait for a server response before failing. * [**Request Body**](https://doc.uforge.co.uk/structs#make-httprequest-settings) – (**Optional**) JSON data or payload to send with the request (used with **POST**, **PUT**, **PATCH**). And header definition. ## Outputs * **Success -** Returns **true** if the request was created successfully. Otherwise, returns **false**. * **Out HTTPRequest** - A proxy instance referencing your **HTTP(S)** request, which must be configured before execution. {% endhint %} *** ### Set HTTP Request Body
{% hint style="info" %} ### Set HTTP Request Body ## Overview This node overrides the **HTTP(S)** request body with the new provided body. It will fully override the body. This is useful for cases where the full body is dynamically populated and needs to be updated. This node must be called before the request is sent. ## Inputs * **Target** – The **HTTP(S)** request object we want to override the body for. The target node must be a child of class "**HTTPProxy**" * [N**ew Request Body**](https://doc.uforge.co.uk/structs#make-http-body) – The new struct that will contain the new body of the request. This will override the current body of the request with the new passed in struct. ## Outputs **None.** {% endhint %} *** ### Set HTTP Request Type
{% hint style="info" %} ### Set HTTP Request Type ## Overview This node overrides the **HTTP(S)** Verb for the specified request. This is a fundamental part of defining how the request will behave and interact with an API endpoint. This is a useful node if the Verb of the **HTTP(S)** request needs to change dynamically. This node must be called before the request is sent. ## Supported Request Types * **GET**– Retrieves data from the server (**default**). * **POST** – Sends data to the server, typically for creating new resources. * **PUT** – Sends data to update/replace a resource. * **PATCH** – Partially updates an existing resource. * **DELETE** – Deletes a resource on the server. * **HEAD** – Retrieves headers only (no body). * **TRACE** – Echoes the received request (**used for diagnostics**). ## Inputs * **Target** – The **HTTP(S)** request object we want to override the Request type for. The target node must be a child of class "**HTTPProxy**" * **New Request Type**– The new request type to override the target **HTTP(S) proxy** request. ## Outputs **None.** {% endhint %} *** ### Delegate - OnSuccess
{% hint style="info" %} ### Delegate OnSuccess ## Overview This node is used to bind a and listen to the event **On Success,** for [non ASYNC **HTTP(S)** request](#create-new-http-request). When the **HTTP** request completes successfully, the bound event is triggered and supplied you with the response data. The event must be bound **before** the request is initiated to ensure proper tracking during execution. ## Inputs * **Target** – The **HTTP(S)** request object we want to bind the delegate from. The target node must be a child of class "**HTTPProxy**" ## Outputs * **Out Json** – Parsed JSON response object. * **Out Binary Data** - If binary-only data is detected, it will be provided here for direct access. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. {% endhint %} *** ### Delegate - OnProgress
{% hint style="info" %} ### Delegate OnProgress ## Overview This node is used to bind and listen to the **On Progress** event for [non-ASYNC **HTTP(S)** requests](#create-new-http-request). It allows you to monitor and respond to the progress of an ongoing **HTTP** request. The event must be bound **before** the request is initiated to ensure proper tracking during execution. ## Inputs * **Target** – The **HTTP(S)** request object we want to bind the delegate from. The target node must be a child of class "**HTTPProxy**" ## Outputs * **Out Json –** Parsed JSON response object. * **Out Binary Data** - If binary-only data is detected, it will be provided here for direct access. * **Response Code** – The response code from the server. {% endhint %} ### Delegate - OnStreamed
{% hint style="info" %} ### Delegate OnStreamed ## Overview This node is used to bind to and listen for the **On Streamed** event for [non-ASYNC HTTP(S) requests](#create-new-http-request). It allows you to receive streamed responses from a server. The event can trigger multiple times as complete chunks of the response are received. ## Inputs * **Target** – The **HTTP(S)** request object we want to bind the delegate from. The target node must be a child of class "**HTTPProxy**" ## Outputs * **Out Json** – Used for **SSE** (**Server-Sent Events**) responses. Events are encoded as JSON, allowing you to extract and use the data. * **Out Binary Data** – Contains the raw binary data. Use this if you are expecting a binary-only response. {% endhint %} *** *** ### Delegate - OnFailed
{% hint style="info" %} ### Delegate OnFailed ## Overview This node is used to bind and listen to the **On Failed** event for [non-ASYNC **HTTP(S)** requests.](#create-new-http-request) If the request fails, either due to a network error, timeout, invalid endpoint, or server-side issue. The bound custom event will be triggered, allowing you to handle the failure. The input pins do not have to be populated with creation of this proxy object. ## Inputs * **Target** – The **HTTP(S)** request object we want to bind the delegate from. The target node must be a child of class "**HTTPProxy**" ## Outputs * **Out Json** – Parsed JSON response object. * **Out Binary Data** - If binary-only data is detected, it will be provided here for direct access. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. **Note:** If an error occurs during the **HTTP Request**. Either from the server or within the node itself. An error message will be returned as a JSON response for you to handle. {% endhint %} *** ## Non ASNYC Multipart Request ### Create New Multipart Request
{% hint style="info" %} ### Create New Multipart Request ## Overview This node mirrors the functionality of the [ASYNC **multipart**](#async-multipart-request) variant but creates a new **non-ASYNC** **HTTP(S) multipart request** instance. Since it is **non-ASYNC**, the request does not need to be sent immediately after creation. The node outputs an **MultipartProxy** object, which can be manually configured and executed at a later time. This setup is ideal for developers who require direct control over how the request is sent, tracked and potentially cancelled. The input pins do not have to be populated with creation of this proxy object. ## Inputs * **URL** – The target URL to which the multipart request will be sent. * **Timeout** – Duration (**in seconds**) to wait for a server response before failing. * [**Multipart Data**](https://doc.uforge.co.uk/structs#make-multipart-http-data) – Struct multipart data to be sent with the request. This includes the main body of the request. ## Outputs * **Success -** Returns **true** if the request was created successfully. Otherwise, returns **false**. * **Out Multipart Request** - A proxy instance referencing your **Multipart** request, which must be configured before execution. {% endhint %} *** ### Add Multi-part Data To Request
{% hint style="info" %} ### Add Multi-part Data To Request ## Overview This node appends additional multipart data to an existing **multipart HTTP request**. It is used in scenarios where you need to include more multipart fields after the initial request object has been constructed. This node must be called before the request is sent. ## Inputs * **Target** – The multipart request object to which the new multipart data will be appended. The target node must be a child of the "**MultipartProxy"** class. * **New Multipart Data** – A map that holds key-value pairs. This map represents the new multipart data you want to add to your request. ## Outputs * **Success -** Returns **true** if the request was created successfully. Otherwise, returns **false**. {% endhint %} *** ### Toggle Random Boundary
{% hint style="info" %} ### Toggle Random Boundary ## Overview This node toggles the "**Random Boundary**" setting used in **multipart** **HTTP** requests. Boundaries are required in multipart formats to separate parts of the request payload. When enabled, a randomly generated boundary will be used. when disabled, a custom boundary must be supplied. This node must be called before the request is sent. ## Inputs * **Target** – The multipart request object to which the new random boundary bool set. The target node must be a child of the "**MultipartProxy"** class. * **New Random Boundary -** Set to **true** to enable random boundary generation, set to **false** to disable it, requiring manual boundary configuration. ## Outputs None. {% endhint %} *** ### Set Random Boundary
{% hint style="info" %} ### Set Random Boundary ## Overview This node sets a custom boundary string for a **multipart HTTP request**. **Multipart** boundaries are used to define where each part of the payload begins and ends. This node gives you manual control over the boundary value when random generation is disabled. This node must be called before the request is sent. **Note:** This node has no effect if the "**Random Boundary**" setting is enabled. To use this node effectively, make sure **random boundary** generation is turned off using the [**Toggle Random Boundary**](#toggle-random-boundary) node, or in the request body. ## Inputs * **Target** – The multipart request object to which the new boundary will be set. The target node must be a child of the "**MultipartProxy"** class. * **New Boundary -** A custom string value to use as the **multipart boundary**. Must follow proper boundary formatting. ## Outputs None. {% endhint %} *** ### Set Request Data
{% hint style="info" %} ### Set Request Data ## Overview This node overrides the entire **multipart body** of a **multipart HTTP reques**t with new **multipart data**. It is used when you want to fully replace the request's contents with a new set of multipart data. This is ideal for situations where you've generated multipart data externally or want to reuse predefined data across multiple requests. This node must be called before the request is sent. ## Inputs * **Target** – The multipart request object whose data is to be overridden. The target must be a child of "**MultipartProxy"** class. * [**New Multipart Data**](https://doc.uforge.co.uk/structs#make-multipart-http-data) **-** The new multipart data that will completely replace the current **multipart payload**. ## Outputs None. {% endhint %} *** ### Delegate - OnSuccess
{% hint style="info" %} ### Delegate OnSuccess ## Overview This node is used to bind a and listen to the event **On Success,** for non ASYNC **multipart HTTP** request. When the **multipart HTTP reques**t completes successfully, the bound event is triggered and supplied you with the response data. The event must be bound **before** the request is initiated to ensure proper tracking during execution. ## Inputs * **Target** – The **multipart HTTP reques**t object we want to bind the delegate from. The target node must be a child of class "MultipartProxy" ## Outputs * **Out Json** – Parsed JSON response object. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. {% endhint %} *** ### Delegate - OnProgress
{% hint style="info" %} ### Delegate OnProgress ## Overview This node is used to bind and listen to the **On Progress** event for non-ASYNC **multipart HTTP** requests. It allows you to monitor and respond to the progress of an ongoing **multipart HTTP** request. The event must be bound **before** the request is initiated to ensure proper tracking during execution. ## Inputs * **Target** – The **multipart HTTP reques**t object we want to bind the delegate from. The target node must be a child of class "MultipartProxy" ## Outputs * **Out Json** – Parsed JSON response object. * **Response Code** – The response code from the server. {% endhint %} *** ### Delegate - OnFailed
{% hint style="info" %} ### Delegate OnFailed ## Overview This node is used to bind and listen to the **On Failed** event for non-ASYNC **multipart HTTP** requests. If the request fails, either due to a network error, timeout, invalid endpoint, or server-side issue. The bound custom event will be triggered, allowing you to handle the failure. The input pins do not have to be populated with creation of this proxy object. ## Inputs * **Target** – The **multipart HTTP reques**t object we want to bind the delegate from. The target node must be a child of class "MultipartProxy" ## Outputs * **Out Json** – Parsed JSON response object. * **Response Code** – The response code from the server. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. **Note:** If an error occurs during the **Multipart request**. Either from the server or within the node itself. An error message will be returned as a JSON response for you to handle. {% endhint %} *** ## Non ASNYC Upload Multipart Request ### Create New Upload Multipart Request
{% hint style="info" %} ### Create New Upload Multipart Request ## Overview This node mirrors the functionality of the [ASYNC **multipart Upload** ](#async-upload-multipart-file)variant but creates a new **non-ASYNC** **upload multipart HTTP** request object. It is specifically designed to send binary files and associated metadata to a specified URL via a **multipart request format**. Unlike regular multipart requests, this version includes dedicated support for file data structures and upload configuration. The node outputs a "**MultipartUploadProxy"** object that can be further customized before executing the upload. ## Inputs * **URL** – The target URL to which the multipart request will be sent. * **Timeout** – Duration (**in seconds**) to wait for a server response before failing. * [**Upload Settings**](https://doc.uforge.co.uk/structs#make-httprequest-settings) **-** A struct that contains core configuration settings for the request, such as boundary definitions and headers. * [**File Data**](https://doc.uforge.co.uk/structs#make-upload-file-data) **-** The primary array containing all the necessary information to construct the upload request. Each entry in the array represents a separate file to be uploaded. ## Outputs * **Success -** Returns **true** if the request was created successfully. Otherwise, returns **false**. * **Out Multipart Request** - A proxy instance referencing your "**MultipartUploadProxy"** request, which must be configured before execution. {% endhint %} *** ### Set File Data
{% hint style="info" %} ### Set File Data ## Overview This node overrides the primary array holding all the files you wish to upload with the new passed in array data. It is typically used when you want to replace all files with new data. This node must be called before the request is sent. ## Inputs * **Target** – The Upload multipart request object whose data is to be overridden. The target must be a child of "**MultipartUploadProxy"** class. * [**New File Data**](https://doc.uforge.co.uk/structs#make-upload-file-data) **-** The new array containing individual file data that will override the existing data. ## Outputs None. {% endhint %} *** ### Add File Binary Data
{% hint style="info" %} ### Add File Binary Data ## Overview This node appends a single binary file entry to the internal file data array used in a **multi-part upload HTTP request**. Unlike [ **Set File Data**](#set-file-data), which replaces the entire array, this node allows incremental addition of individual files without overriding existing entries. Useful when constructing file uploads dynamically. ## Inputs * **Target** – The multipart request instance to which the new binary file will be added. The target must be a child of "**MultipartUploadProxy"** class. * [**New File Data**](https://doc.uforge.co.uk/structs#make-upload-file-data) **-** The data for the new file to be uploaded. This includes metadata such as file name, content type, and the binary payload. ## Outputs None. {% endhint %} *** ### Set Upload Settings
{% hint style="info" %} ### Set Upload Settings ## Overview This node overrides the current upload configuration of a **multipart upload request** by applying a new set of upload settings. These settings control how the **multipart HTTP Upload request** will behave. Such as the boundary string used or headers. ## Inputs * **Target** – The multipart request instance whose settings will be overridden. The target must be a child of "**MultipartUploadProxy"** class. * [**New Upload Settings**](https://doc.uforge.co.uk/structs#make-httprequest-settings) **-** The new settings structure containing configuration for the **Multipart Upload Request.** ## Outputs None. {% endhint %} *** ### Toggle Random Boundary
{% hint style="info" %} ### Toggle Random Boundary ## Overview This node toggles the "**Random Boundary**" setting used in **multi-part upload HTTP** requests. Boundaries are required in multipart formats to separate parts of the request payload. When enabled, a randomly generated boundary will be used. when disabled, a custom boundary must be supplied. This node must be called before the request is sent. ## Inputs * **Target**– The multipart request object to which the new random boundary bool set. The target node must be a child of the "**MultipartUploadProxy"** class. * **New Random Boundary**: Set to **true** to enable random boundary generation, set to **false** to disable it, requiring manual boundary configuration. ## Outputs None. {% endhint %} *** ### Set Random Boundary
{% hint style="info" %} ### Set Random Boundary ## Overview This node sets a custom boundary string for a **multi-part upload HTTP request**. **Multipart** boundaries are used to define where each part of the payload begins and ends. This node gives you manual control over the boundary value when random generation is disabled. This node must be called before the request is sent. **Note:** This node has no effect if the "**Random Boundary**" setting is enabled. To use this node effectively, make sure **random boundary** generation is turned off using the [**Toggle Random Boundary**](#toggle-random-boundary-2) node, or in the request body. ## Inputs * **Target**– The multipart request object to which the new boundary will be set. The target node must be a child of the "**MultipartUploadProxy"** class. * **New Boundary:** A custom string value to use as the **multipart boundary**. Must follow proper boundary formatting. ## Outputs None. {% endhint %} *** ### Delegate - OnSuccess
{% hint style="info" %} ### Delegate OnSuccess ## Overview This node is used to bind a and listen to the event **On Success,** for non ASYNC **multi-part upload HTTP** request. When the **multi-part upload HTTP reques**t completes successfully, the bound event is triggered and supplied you with the response data. The event must be bound **before** the request is initiated to ensure proper tracking during execution. ## Inputs * **Target** – The **multi-part upload HTTP reques**t object we want to bind the delegate from. The target node must be a child of class "**MultipartUploadProxy**" ## Outputs * **Out Json** – Parsed JSON response object. * **Response Code** – The HTTP status code. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. {% endhint %} *** ### Delegate - OnProgress
{% hint style="info" %} ### Delegate OnProgress ## Overview This node is used to bind and listen to the **On Progress** event for non-ASYNC **multi-part upload HTTP** requests. It allows you to monitor and respond to the progress of an ongoing **multi-part upload HTTP** request. The event must be bound **before** the request is initiated to ensure proper tracking during execution. ## Inputs * **Target** – The **multi-part upload HTTP reques**t object we want to bind the delegate from. The target node must be a child of class "**MultipartUploadProxy**" ## Outputs **None.** {% endhint %} *** ### Delegate - OnFailed
{% hint style="info" %} ### Delegate OnFailed ## Overview This node is used to bind and listen to the **On Failed** event for non-ASYNC **multi-part upload HTTP** requests. If the request fails, either due to a network error, timeout, invalid endpoint, or server-side issue. The bound custom event will be triggered, allowing you to handle the failure. The input pins do not have to be populated with creation of this proxy object. ## Inputs * **Target** – The **multi-part upload HTTP reques**t object we want to bind the delegate from. The target node must be a child of class "**MultipartUploadProxy**" ## Outputs * **Out Json** – Parsed JSON response object. * **Response Code** – The HTTP status code. * **Content Type** – The Content-Type header of the server response. * **Response Headers** – An array of all headers returned by the server. **Note:** If an error occurs during the **Multipart upload request**. Either from the server or within the node itself. An error message will be returned as a JSON response for you to handle. {% endhint %}