# Fang URLs

## Description

This operation takes a 'defanged' URL and 'fangs' it, meaning, it removes the alterations that render it useless so that it can be used again.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

![](/files/lPHCVhp93aYrWgLIlhNp) - URLs you want to fang.

### Output data

![](/files/3itBmKrRqasWlG3dGBlS) - Valid URLs.

***

## Parameters

These are the parameters you need to configure to use this operation (mandatory parameters are marked with a \*):

<details>

<summary>Escape Dots<mark style="color:red;"><strong>*</strong></mark></summary>

Set this parameter to **true** if you want to restore `.` in the URL domains. For example, `example[.]com` becomes `example.com`.

</details>

<details>

<summary>Escape HTTP<mark style="color:red;"><strong>*</strong></mark></summary>

Set this parameter to **true** if you want to restore `hxxp` or `hxxps` and make them `http` or `https`, respectively.

</details>

<details>

<summary>Escape ://<mark style="color:red;"><strong>*</strong></mark></summary>

Set this parameter to **true** if you want to restore the `://` separator in your URLs.

</details>

***

## Example

Suppose you want to **fang** a series of events that represent **URLs**:

1. In your Pipeline, open the required [Action](/the-workspace/pipelines/actions.md) configuration and select the input **Field**.
2. In the **Operation** field, choose **Fang URL**.
3. Set **Escape Dots** to **true**.
4. Set **Escape HTTP** to **true**.
5. Set **Escape ://\*** to **false**.
6. Give your **Output field** a name and click **Save**. The URLs in your input field will be made valid. For example:

```
Input data - "hxxps://example[.]com"

Escape Dots - true

Escape HTTP - true

Escape ://* - false

Output data - "https://example.com"
```

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}


---

# 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.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/networking/fang-urls.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.