From 068124d9d249b4db8454a2ae72fba772979f921a Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 08:53:19 -0300 Subject: [PATCH 01/10] refactor: change protect domain steps on english guides --- .../integrations/add-request-id.mdx | 26 ++++++++++++------- .../integrations/bot-manager-lite.mdx | 5 ++-- .../guides/marketplace/integrations/ipqs.mdx | 19 +++++++++----- .../guides/marketplace/integrations/jwt.mdx | 23 ++++++++++------ .../integrations/limit-payload.mdx | 23 ++++++++++------ .../integrations/radware-bot-manager.mdx | 19 +++++++++----- .../rate-limiting-with-penalty.mdx | 25 +++++++++++------- .../marketplace/integrations/recaptcha.mdx | 17 ++++++++---- .../integrations/request-data-into-header.mdx | 22 +++++++++++----- .../integrations/scheduled-blocking.mdx | 21 ++++++++++----- .../marketplace/integrations/secure-token.mdx | 23 ++++++++++------ .../integrations/send-event-endpoint.mdx | 20 +++++++++----- .../marketplace/integrations/waiting-room.mdx | 23 +++++++++------- 13 files changed, 174 insertions(+), 92 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx index 4335a91b71..9a4d216698 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx @@ -63,9 +63,8 @@ To do so, follow the steps: 1. On the upper-left corner, select **Products menu** > **Edge Firewall** in the **Secure** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Enable the **Edge Functions** switch in the **Modules** section. -6. Click the **Save** button. +4. Enable the **Edge Functions** switch in the **Modules** section. +5. Click the **Save** button. Done. Now you've instantiated the edge firewall for your integration and it has access to edge functions. @@ -153,12 +152,19 @@ Still in the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. -3. Give an easy-to-remember name to the rule. - - You can add a description, but it's an optional step. -4. Select a *criteria* to run and catch the domains that you want to run the integration on. Example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. -5. Below, select a *behavior* **Run Function**. -6. Select the adequate function according to the name you gave it in the previous step. -7. Click the **Save** button. +3. Give a name to the rule. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. +6. Click the **Save** button. + +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Add Request ID function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. Done. You've now configured the **Add Request ID** integration and will start receiving the header. @@ -176,4 +182,4 @@ Done. You've now configured the **Add Request ID** integration and will start re Done. You've now configured the **Add Request ID** integration and will start receiving the header. - \ No newline at end of file + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx index b870695d11..7e372ff268 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx @@ -71,9 +71,8 @@ To instantiate Azion **Bot Manager Lite**, follow the steps: 1. On the upper-left corner, select **Products menu** > **Edge Firewall** in the **Secure** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your new edge firewall. -4. Select the domains you want to protect with the function. -5. Enable the **Edge Functions** switch in the **Modules** section. -6. Click the **Save** button. +4. Enable the **Edge Functions** switch in the **Modules** section. +5. Click the **Save** button. Done. Now you've configured your edge firewall and it has access to Edge Functions. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx index c39c0e35aa..680a21b57e 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx @@ -77,7 +77,6 @@ To start the configuration of the **IP Address Reputation** integration, follow 1. On the **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -3. Select the domains you want to protect with the function. 4. Click the **Edge Functions** switch to enable functions. 5. Click the **Save** button. @@ -88,9 +87,9 @@ Done. Now you've instantiated the edge firewall for your function. 1. On the **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **Add Rule Set** button. 3. Give an easy-to-remember name to your edge firewall. -3. Select the domains you want to protect with the function. -4. Click the **Edge Functions** switch to enable functions. -5. Click the **Save** button. +4. Select the domains you want to protect with the function. +5. Click the **Edge Functions** switch to enable functions. +6. Click the **Save** button. Done. Now you've instantiated the edge firewall for your function. @@ -203,11 +202,19 @@ Still on the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a criteria to run and catch the domain you want to run the integration on. Example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate IP Address Reputation function according to the name you gave it in the instantiation step. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your IP Address Reputation function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now the IP Address Reputation integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx index 362d02ca17..a4891ca502 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx @@ -65,9 +65,8 @@ To instantiate the JWT Edge Function, follow these steps: 1. On the upper-left corner, open the **Products menu**, represented by three horizontal lines, then select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give a name to your edge firewall. -4. Select the domains you want to protect with the JWT Edge Function. -5. Click the **Edge Functions** switch. -6. Click the **Save** button. +4. Click the **Edge Functions** switch. +5. Click the **Save** button. @@ -156,14 +155,22 @@ To do so, still on the **Edge Firewall** page, follow these steps: Real-Time Manager -1. Go to the **Rules Engine** tab. +1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a criteria with the domain that will run the integration. For example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. -5. Below, select the **Run Function** *behavior* to the *criteria*. - - Select the adequate **JWT function** according to the name you gave it in the instantiate step. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your JWT function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now you have a JWT integration running for every request made to the domain you indicate. @@ -183,4 +190,4 @@ Done. Now you have a JWT integration running for every request made to the domai :::tip You can see a use case by visiting the [Setting up a paywall with Edge Function JWT](/en/documentation/products/guides/paywall-edge-function-jwt/) page. -::: \ No newline at end of file +::: diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx index e02578077d..ecd391e3a2 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx @@ -67,9 +67,8 @@ To instantiate the **Limit Payload Size** integration, follow the steps: 1. On the **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy to remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Click the **Edge Functions** switch to enable functions on your edge firewall. -6. Click the **Save** button. +4. Click the **Edge Functions** switch to enable functions on your edge firewall. +5. Click the **Save** button. Done. Now you've instantiated the edge firewall for your function. @@ -165,10 +164,18 @@ Still on the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a *criteria* to run and catch the domain you want to run the integration on. -5. Below, select a behavior to the *criteria*. In this case, it'll be a **Run Function**. -6. Select the adequate **Limit Payload Size** function according to the name you gave it in the instantiate step. -7. Click the **Save** button. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. +6. Click the **Save** button. + +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Limit Payload Size function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. Done. Now the Limit Payload Size integration is running for every request made to the domain you indicated. @@ -185,4 +192,4 @@ Done. Now the Limit Payload Size integration is running for every request made t Done. Now the Limit Payload Size integration is running for every request made to the domain you indicated. - \ No newline at end of file + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx index 7c93cc82f6..ece63602ff 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx @@ -65,9 +65,8 @@ To instantiate the **Radware Bot Manager** integration, follow the steps: 1. Under **Products Menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give a name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Click the **Edge Functions** switch to enable functions on your edge application. -6. Click the **Save** button. +4. Click the **Edge Functions** switch to enable functions on your edge application. +5. Click the **Save** button. Done. Now you have instantiated the edge firewall for your function. @@ -163,11 +162,19 @@ Still in the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a *criteria* to run and catch the domains that you want to run the integration on. For example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate **Radware Bot Manager** function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Radware Bot Manager function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now the **Radware Bot Manager** integration is running for every request made to the domain you indicated. @@ -183,4 +190,4 @@ Done. Now the **Radware Bot Manager** integration is running for every request m Done. Now the **Radware Bot Manager** integration is running for every request made to the domain you indicated. - \ No newline at end of file + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx index f9d995db64..ac47dc25d9 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx @@ -81,10 +81,9 @@ To instantiate the **Upstash Rate Limiting** integration, follow the steps: 1. Open the **Products menu** and select **Edge Firewall** in the **Secure** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Enable the **Edge Functions** switch in the **Modules** section. +4. Enable the **Edge Functions** switch in the **Modules** section. - This action gives access to edge functions on your edge firewall. -6. Click the **Save** button. +5. Click the **Save** button. Done. Now you've instantiated the edge firewall for your function. @@ -315,11 +314,19 @@ Still in the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. -3. Give an easy-to-remember name to the rule. -4. Select a *criteria* to run and catch the domains that you want to run the integration on. Example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. -5. Below, select the **Run Function** *behavior* to the *criteria*. -6. Select the **Upstash Rate Limiting** function according to the name you gave it before. -7. Click the **Save** button. +3. Give a name to the rule. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. +6. Click the **Save** button. + +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Upstash Rate Limiting function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. Done. Now **Upstash Rate Limiting** is running and protecting your domains. @@ -340,4 +347,4 @@ Done. Now **Upstash Rate Limiting** is running and protecting your domains. Discover how to enhance your web application's performance with this tutorial on **Rate Limit with Penalty on Azion + Upstash DB**. Watch now on Azion's YouTube channel. - \ No newline at end of file + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx index dd877b5ada..bd89c69dfd 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx @@ -90,9 +90,8 @@ To start the configuration of the **reCAPTCHA** integration, follow these steps: 1. On the **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Click the **Edge Functions** switch to enable functions. -6. Click the **Save** button. +4. Click the **Edge Functions** switch to enable functions. +5. Click the **Save** button. Done. Now you have instantiated the rule for your function. @@ -238,11 +237,19 @@ Still on the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a *criteria* to run and catch the domain you want to run the integrationn on. Example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate **reCAPTCHA** function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your reCAPTCHA function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now the **reCAPTCHA** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx index 19238bfea9..22983d9f61 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx @@ -67,9 +67,8 @@ To instantiate the **Process Request Data Into Header** integration, follow the 1. On the **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy to remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Turn the **Edge Functions** switch on. -6. Click the **Save** button. +4. Turn the **Edge Functions** switch on. +5. Click the **Save** button. Done. Now you have instantiated the rule for your function. @@ -151,11 +150,20 @@ Still in the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. -3. Name your rule something easy to remember. -4. Select a *criteria* to run and catch the domain you want to run the integration on. -5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. Then, select the adequate **Process Request Data Into Header** function, according to the name you gave it in the instantiate step. +3. Give a name to the rule. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your IP Process Request Data Into Header. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now the **Process Request Data Into Header** integration is running for every request made to the domain you indicated. @@ -170,4 +178,4 @@ Done. Now the **Process Request Data Into Header** integration is running for ev Done. Now the **Process Request Data Into Header** integration is running for every request made to the domain you indicated. - \ No newline at end of file + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx index ecfa5033e1..af173a0315 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx @@ -65,9 +65,8 @@ To instantiate the **Scheduled Blocking** integration, follow the steps: 1. In the **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Turn the **Edge Functions** switch on. -6. Click the **Save** button. +4. Turn the **Edge Functions** switch on. +5. Click the **Save** button. Done. Now you've instantiated the edge firewall for your function. @@ -280,11 +279,19 @@ Still in the **Edge Firewall** page. 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a criteria to run and catch the domain you want to run the integration on. -5. Below, select the **Run Function** *behavior* to the *criteria*. - - Select the adequate **Scheduled Blocking** function according to the name you gave it in the instantiate step. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Scheduled Blocking function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now the Scheduled Blocking integration is running for every request made to the domain you indicated. @@ -300,4 +307,4 @@ Done. Now the Scheduled Blocking integration is running for every request made t Done. Now the Scheduled Blocking integration is running for every request made to the domain you indicated. - \ No newline at end of file + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index 28be1bd62b..74172d7fac 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -101,9 +101,8 @@ To instantiate the **Secure Token** integration, follow the steps: 1. In the **Products menu**, select **Edge Firewall** in the **Secure** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Turn the **Edge Functions** switch on. -6. Click the **Save** button. +4. Turn the **Edge Functions** switch on. +5. Click the **Save** button. Done. Now you've instantiated the edge firewall for your function. @@ -183,14 +182,22 @@ Still in the **Edge Firewall** page: Real-Time Manager -1. Select the **Rules Engine** tab and follow these steps: +1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. 3. Give a name to the rule. -4. Select a *criteria* to run and catch the domain you want to run the integration on. For example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net/classes`. -5. Below, select the **Run Function** *behavior* to the *criteria*. - - Select the adequate **Secure Token** function according to the name you gave it in the instantiate step. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Secure Token function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + :::note The edge function running on edge servers performs two checks on tokens: whether the current time is greater than the expiration time specified in the token, and whether the signature matches the token signature. If the signature is invalid, the system returns a 403 error, and if the expiry time is exceeded, it returns a 410 error. Malicious users aren't able to change token expiry time without breaking signature. ::: @@ -218,4 +225,4 @@ Done. Now the **Secure Token** integration is running for every request made to :::tip You can find some examples of code snippets at the [Azion public GitHub repository](https://github.com/aziontech/azion_secure_token) for Secure Token integration. -::: \ No newline at end of file +::: diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx index 0c4e9d796d..ee690fbd75 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx @@ -67,9 +67,8 @@ To instantiate the **Send Event to Endpoint** integration, follow these steps: 1. Under **Products menu**, select **Edge Firewall** in the **SECURE** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy to remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Turn the **Edge Functions** switch on. -6. Click the **Save** button. +4. Turn the **Edge Functions** switch on. +5. Click the **Save** button. Done. Now you have instantiated the edge firewall for your function. @@ -344,11 +343,20 @@ Still in the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. -3. Give an easy to remember name to the rule. -4. Select a *criteria* to run and catch the domain you want to run the integration on. For example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. -5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. Then, select the adequate **Send Event to Endpoint** function according to the name you gave it in the instantiating step. +3. Give a name to the rule. +4. Select a *criteria* to run and catch the domains that you want to run the integration on. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Send Event to Endpoint function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. + Done. Now the **Send Event to Endpoint** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx index 15cf8761a4..8f003918ac 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx @@ -76,10 +76,8 @@ Follow the steps: 1. On the upper-left corner, open the **Products menu** and select **Edge Firewall** in the **Secure** section. 2. Click the **+ Edge Firewall** button. 3. Give an easy-to-remember name to your edge firewall. -4. Select the domains you want to protect with the function. -5. Enable the **Edge Functions** switch in the **Modules** section. - - This action gives access to edge functions on your edge firewall. -6. Click the **Save** button. +4. Turn the **Edge Functions** switch on. +5. Click the **Save** button. Done. Now you've instantiated the edge firewall for your function and have access to edge functions on your edge firewall. @@ -188,12 +186,19 @@ Still in the **Edge Firewall** page: 1. Select the **Rules Engine** tab. 2. Click the **+ Rule Engine** button. -3. Give an easy-to-remember name to the rule. +3. Give a name to the rule. 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - - Example: if `Request URI` *starts with* `./`. -5. Below, select the **Run Function** *behavior* to the *criteria*. -6. Select the **Upstash Waiting Room** function according to the name you gave it before. -7. Click the **Save** button. + - Example: if `Host` *matches* `yourdomain.com`. +5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. + - Select the adequate function according to the name you gave it in the instantiate step. +6. Click the **Save** button. + +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +7. On the **Products menu**, select **Domains**. +8. Click on the domain you want to protect with your Upstash Waiting Room function. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +10. Click the **Save** button. Done. Now the **Upstash Waiting Room** integration is running. From 504cbf2cfea95e8a77b4141cadbc5b06fc3e6fb4 Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 09:15:40 -0300 Subject: [PATCH 02/10] refactor: change protect domain steps on pt-br guides --- .../integrations/add-request-id.mdx | 26 +++++++++++------- .../integrations/bot-manager-lite.mdx | 12 ++++++--- .../guias/marketplace/integrations/ipqs.mdx | 21 ++++++++++----- .../guias/marketplace/integrations/jwt.mdx | 25 ++++++++++------- .../integrations/limit-payload.mdx | 24 +++++++++++------ .../integrations/radware-bot-manager.mdx | 25 ++++++++++------- .../integrations/rate-limit-with-penalty.mdx | 22 +++++++++------ .../marketplace/integrations/recaptcha.mdx | 19 ++++++++----- .../integrations/request-data-headers.mdx | 24 +++++++++++------ .../integrations/scheduled-blocking.mdx | 27 ++++++++++++------- .../marketplace/integrations/secure-token.mdx | 23 ++++++++++------ .../integrations/send-event-endpoint.mdx | 18 +++++++++---- .../marketplace/integrations/waiting-room.mdx | 20 +++++++++----- 13 files changed, 188 insertions(+), 98 deletions(-) diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx index 342f3d0f92..607433fa2b 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx @@ -63,9 +63,8 @@ Siga estes passos: 1. No canto superior esquerdo, abra o **Products menu** e selecione **Edge Firewall** na seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -4. Selecione os domínios que deseja proteger com a função. -5. Ative a opção **Edge Functions** na seção **Modules**. -6. Clique no botão **Save**. +4. Ative a opção **Edge Functions** na seção **Modules**. +5. Clique no botão **Save**. Pronto. Agora você instanciou o edge firewall para sua função e tem acesso a edge functions em seu edge firewall. @@ -153,12 +152,19 @@ Ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome fácil de lembrar para a regra. - - Você pode adicionar uma descrição, mas é um passo opcional. -4. Selecione um *criteria* para executar e capturar os domínios em que você deseja executar a integração. -5. Logo, selecione o *behavior* **Run Function**. -6. Selecione a função adequada de acordo com o nome que você deu a ela na etapa de instanciação. -7. Clique no botão **Save**. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Add Request ID**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Você agora configurou a integração **Add Request ID** e começará a receber o cabeçalho. @@ -176,4 +182,4 @@ Pronto. Você agora configurou a integração **Add Request ID** e começará a Pronto. Você agora configurou a integração **Add Request ID** e começará a receber o cabeçalho. - \ No newline at end of file + diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx index ff86a0b556..dbfca26bf3 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx @@ -72,9 +72,8 @@ Para instanciar a integração Azion **Bot Manager Lite**, siga estes passos: 1. No canto superior esquerdo, selecione **Products menu** > **Edge Firewall**, dentro da seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu novo edge firewall. -4. Selecione os domínios que deseja proteger com a função. -5. Habilite o switch **Edge Functions** na seção **Modules**. -6. Clique no botão **Next**. +4. Habilite o switch **Edge Functions** na seção **Modules**. +5. Clique no botão **Next**. Pronto. Você criou uma instância no Edge Firewall para sua função e habilitou o uso de Edge Functions nele. @@ -218,6 +217,13 @@ Ainda na página **Edge Firewall**: 7. Selecione a função de acordo com o nome que você deu no passo 3. 8. Clique no botão **Save**. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +9. No **Products menu**, selecione **Domains**. +10. Clique no domínio que você deseja proteger com sua função **Bot Manager Lite**. +11. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +12. Clique no botão **Save**. + Pronto. Agora você tem seus domínios protegidos contra ataques de bot usando a integração Azion **Bot Manager Lite**. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx index e93e9e6c15..fcb959bf9d 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx @@ -79,7 +79,6 @@ Para iniciar a configuração da integração **IP Address Reputation**, complet 1. No **Products menu**, selecione **Edge Firewall** na seção **SECURE**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -3. Selecione os domínios que deseja proteger com a função. 4. Clique no switch de **Edge Functions** para ativar as funções. 5. Clique no botão **Save**. @@ -90,9 +89,9 @@ Pronto. Você instanciou um edge firewall para sua função. 1. No **Products menu**, selecione **Edge Firewall** na seção **SECURE**. 2. Clique no botão **Add Rule Set**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -3. Selecione os domínios que deseja proteger com a função. -4. Clique no switch de **Edge Functions** para ativar as funções. -5. Clique no botão **Save**. +4. Selecione os domínios que deseja proteger com a função. +5. Clique no switch de **Edge Functions** para ativar as funções. +6. Clique no botão **Save**. Pronto. Você instanciou um edge firewall para sua função. @@ -204,12 +203,20 @@ Ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome à regra. -4. Selecione um criteria para executar e selecione os domínios nos quais você deseja executar a integração. Exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net/classes`. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. 5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. - - Selecione a função IP Address Reputation adequada de acordo com o nome que você forneceu na etapa de instanciação. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **IP Address Reputation**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. + Pronto. Agora, a integração está em execução para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx index 0d9ad57c58..f419ad8581 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx @@ -65,9 +65,8 @@ JWT é um integração que funciona no **Edge Firewall**. Para ativá-la, você 1. No **Products menu**, selecione **Edge Firewall** na seção **SECURE**. 2. Clique no botão **+ Edge Firewall**. 3. Escolha um nome fácil de lembrar para o seu edge firewall. -4. Selecione os domínios onde a sua integração irá atuar. -5. Ative o switch de **Edge Functions**. -6. Clique no botão **Save**. +4. Ative o switch de **Edge Functions**. +5. Clique no botão **Save**. @@ -158,11 +157,19 @@ Para isso, ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Escolha um nome fácil de lembrar para a sua regra. -4. Selecione um critério (*criteria*) a ser executado quando o domínio em questão for requisitado. Por exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. -5. Abaixo, selecione o **Run Function** *behavior* (comportamento) para os *criteria* (critérios). - - Selecione a function *JWT*, que aparecerá com o nome que você indicou no passo de instanciação. -6. Clique em **Save**. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **JWT**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Agora você tem uma integração **JWT** rodando na sua aplicação para cada requisição que for feita ao seu domínio. @@ -183,4 +190,4 @@ Pronto. Agora você tem uma integração **JWT** rodando na sua aplicação para :::tip Veja exemplos casos de uso para essa integração acessando a página [Configure um paywall com Edge Function JWT](/pt-br/documentacao/produtos/guias/paywall-edge-function-jwt/). -::: \ No newline at end of file +::: diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx index da1b4d1a90..a72d77ca21 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx @@ -13,7 +13,7 @@ import InterfaceNote from '~/includes/snippets/InterfaceNote/pt/snippet.mdx' -**Limite Payload Size** é uma integração *serverless* disponível no Marketplace da Azion. Esta integração emprega uma edge function para avaliar os dados de uma request e negar payloads que excedam o limite pré-definido. +**Limit Payload Size** é uma integração *serverless* disponível no Marketplace da Azion. Esta integração emprega uma edge function para avaliar os dados de uma request e negar payloads que excedam o limite pré-definido. A função valida o tamanho do payload da request, verificando o cabeçalho `Content-Length`. O cabeçalho `Content-Length` é necessário para tornar segura a sua leitura, ao invés de sempre ler o `body` da request. Desta maneira, os usuários estão protegidos contra tentativas de alterar o valor do cabeçalho e a leitura do `Content-Length` é o melhor curso de ação do ponto de vista de desempenho. @@ -164,11 +164,19 @@ Ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome fácil de lembrar para sua regra. -4. Selecione o *criteria* que deseja usar para a execução e o domínio no qual você deseja rodar a integração. -5. Abaixo, selecione um *behavior* para este *criteria*. Neste caso, será **Run Function**. -6. Em seguida, selecione a função **Limite Payload Size**, de acordo com o nome que você deu no passo de instanciação. -7. Clique no botão **Save**. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Limit Payload Size**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Agora a integração está sendo executada para cada request feita ao domínio que você indicou. @@ -179,10 +187,10 @@ Pronto. Agora a integração está sendo executada para cada request feita ao do 3. Dê um nome fácil de lembrar para sua regra. 4. Selecione o *criteria* que deseja usar para a execução e o domínio no qual você deseja rodar a integração. 5. Abaixo, selecione um *behavior* para este *criteria*. Neste caso, será **Run Function**. -6. Em seguida, selecione a função **Limite Payload Size**, de acordo com o nome que você deu no passo de instanciação. +6. Em seguida, selecione a função **Limit Payload Size**, de acordo com o nome que você deu no passo de instanciação. 7. Clique no botão **Save**. Pronto. Agora a integração está sendo executada para cada request feita ao domínio que você indicou. - \ No newline at end of file + diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx index 04a55eaf51..0c3af805a4 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx @@ -63,9 +63,8 @@ Para instanciar a integração **Radware Bot Manager**, siga estes passos: 1. Em **Products Menu**, selecione **Edge Firewall** dentro da seção **SECURE**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome ao edge firewall. -4. Selecione os domínios que você deseja proteger. -5. Habilite o switch de **Edge Functions**. -6. Clique no botão **Save**. +4. Habilite o switch de **Edge Functions**. +5. Clique no botão **Save**. Pronto. Agora você instanciou um edge firewall para a sua integração. @@ -160,11 +159,19 @@ Ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome para a regra. -4. Selecione um *criteria* para executar e selecione os domínios nos quais você deseja executar a integração. Por exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. -5. Abaixo, selecione um behavior para o criteria indicado (você pode indicar mais de um clicando em *AND*). Neste caso, será **Run Function**. - - Selecione a function **Radware Bot Manager**, que aparecerá com o nome que você indicou no passo de instanciação. -6. Clique em **Save**. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Radware Bot Manager**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Agora a integração **Radware Bot Manager** está em execução para cada requisição feita ao domínio que você indicou. @@ -181,4 +188,4 @@ Pronto. Agora a integração **Radware Bot Manager** está em execução para ca Pronto. Agora a integração **Radware Bot Manager** está em execução para cada requisição feita ao domínio que você indicou. - \ No newline at end of file + diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx index b4b5d1dcb9..4db3a13192 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx @@ -83,10 +83,8 @@ Para instanciar a integração **Upstash Rate Limiting**, siga os passos: 1. No **Products menu**, selecione **Edge Firewall** na seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -4. Selecione os domínios que deseja proteger. -5. Ative a opção **Edge Functions** na seção **Modules**. - - Esta ação dá acesso a edge functions no seu edge firewall. -6. Clique no botão **Save**. +4. Ative a opção **Edge Functions** na seção **Modules**. +5. Clique no botão **Save**. Pronto. Você instanciou um edge firewall para sua função. @@ -318,10 +316,18 @@ Ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. 3. Dê um nome fácil de lembrar à sua nova regra. -4. Selecione um *criteria* para executar a integração. Por exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net/classes`. -5. Abaixo, selecione o *behavior* **Run Function**. -6. Selecione a função de **Upstash Rate Limiting** de acordo com o nome que você deu antes. -7. Clique no botão **Save**. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Upstash Rate Limiting**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Agora, **Upstash Rate Limiting** está em execução e protegendo seus domínios. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx index 9a621c8404..d32c4be740 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx @@ -92,9 +92,8 @@ Para iniciar a configuração da **reCaptcha**, complete estes passos: 1. No **Products menu**, selecione **Edge Firewall** na seção **SECURE**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao edge firewall. -4. Selecione os domínios que deseja proteger com a função. -5. Habilite o switch **Edge Functions** para habilitar que você rode edge functions. -6. Clique no botão **Save**. +4. Habilite o switch **Edge Functions** para habilitar que você rode edge functions. +5. Clique no botão **Save**. Pronto. Você instanciou o edge firewall para sua função. @@ -239,12 +238,20 @@ Ainda na página do **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome à regra. -4. Selecione um criteria para executar e selecione os domínios nos quais você deseja executar a integração. Exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net/classes`. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. 5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. - - Selecione a função reCaptcha adequada de acordo com o nome que você deu na etapa de instanciação. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **reCAPTCHA**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. + Pronto. Agora a integração **reCAPTCHA** está em execução para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx index a7b88e2de4..3b97066e8e 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx @@ -67,9 +67,8 @@ Para instanciar a integração **Process Request Data Into Header**, siga os pas 1. No **Products menu**, selecione **Edge Firewall** na seção **SECURE**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar para seu edge firewall. -4. Selecione os domínios que você deseja proteger com a função. -5. Habilite o switch **Edge Functions**. -6. Clique no botão **Save**. +4. Habilite o switch **Edge Functions**. +5. Clique no botão **Save**. Pronto. Agora você instanciou um edge firewall para sua função. @@ -149,13 +148,22 @@ Ainda na página do **Edge Firewall**: Real-Time Manager -1. Selecione a aba **Rules Engine** e siga estes passos: +1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome fácil de lembrar para sua regra. -4. Selecione o *criteria* que deseja usar para executar a integração e o domínio no qual você deseja rodá-la. -5. Abaixo, selecione um *behavior* para este *criteria*. Neste caso, será **Run Function**. Em seguida, selecione a função **Process Request Data Into Header**, de acordo com o nome que você deu no passo de instanciação. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Process Request Data Into Headers**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. + Pronto. Agora a integração está sendo executada para cada requisição feita ao domínio que você indicou. @@ -170,4 +178,4 @@ Pronto. Agora a integração está sendo executada para cada requisição feita Pronto. Agora a integração está sendo executada para cada requisição feita ao domínio que você indicou. - \ No newline at end of file + diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx index 0a9a3580ba..f41ee866b5 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx @@ -65,9 +65,8 @@ Para instanciar a integração **Scheduled Blocking**, siga as etapas: 1. Em **Products menu**, selecione **Edge Firewall** dentro da seção **SECURE**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar para o seu edge firewall. -4. Selecione os domínios que você deseja proteger. -5. Habilite o switch **Edge Functions** para que você rode edge functions no seu edge firewall. -6. Clique no botão **Save**. +4. Habilite o switch **Edge Functions** para que você rode edge functions no seu edge firewall. +5. Clique no botão **Save**. Pronto. Agora você instanciou o edge firewall para sua função. @@ -281,13 +280,21 @@ Ainda na página **Edge Firewall**: Real-Time Manager -1. Selecione a aba **Rules Engine** e siga estes passos: +1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome fácil de lembrar para a sua regra. -4. Selecione um *criteria* para executar e selecione os domínios nos quais você deseja executar a integração. -5. Abaixo, selecione o **Run Function** *behavior* (comportamento) para os *criteria* (critérios). - - Selecione a função de **Scheduled Blocking** adequada de acordo com o nome que você deu na etapa instanciada. -6. Clicar no botão **Save**. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Scheduled Blocking**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Agora, a integração **Scheduled Blocking** está em execução para cada requisição feita ao domínio que você indicou. @@ -304,4 +311,4 @@ Pronto. Agora, a integração **Scheduled Blocking** está em execução para ca Pronto. Agora, a integração **Scheduled Blocking** está em execução para cada requisição feita ao domínio que você indicou. - \ No newline at end of file + diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx index 0626431628..3994803a6a 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx @@ -101,9 +101,8 @@ Para iniciar este processo, siga os passos: 1. No **Products menu**, selecione **Edge Firewall** na seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -4. Selecione os domínios que deseja proteger com a função. -5. Habilite o switch para **Edge Functions**. -6. Clique no botão **Save**. +4. Habilite o switch para **Edge Functions**. +5. Clique no botão **Save**. Pronto. Agora você instanciou o edge firewall para sua função. @@ -185,12 +184,20 @@ Ainda na página **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. -3. Dê um nome fácil de se lembrar para a regra. -4. Selecione um *criteria *para executar a integração. Por exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net/classes`. -5. Abaixo, selecione o **Run Function** *behavior* (comportamento) para os *criteria* (critérios). - - Selecione a função **Secure Token** de acordo com o nome que você deu a ela na etapa instanciada. +3. Dê um nome fácil de lembrar à sua nova regra. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Secure Token**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. + :::note A edge function sendo executada no edge roda duas verificações em tokens: se o tempo atual é maior que o tempo de expiração especificado no token e se a assinatura corresponde à assinatura do token. Se a assinatura for inválida, o sistema retornará um **erro 403** e, se o tempo de expiração for excedido, retornará um **erro 410**. Usuários mal-intencionados não podem alterar o tempo de expiração do token sem quebrar a assinatura. ::: @@ -218,4 +225,4 @@ Pronto. Agora, a integração **Secure Token** está em execução para cada req :::tip Você pode encontrar alguns exemplos de trechos de código no [repositório público do GitHub da Azion](https://github.com/aziontech/azion_secure_token) para a integração Secure Token. -::: \ No newline at end of file +::: diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx index 641e26e97d..502937950a 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx @@ -67,9 +67,8 @@ Para iniciar este processo, siga os passos: 1. Em **Products menu**, selecione **Edge Firewall** na seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -4. Selecione os domínios que deseja proteger com a função. -5. Habilite o switch para **Edge Functions**. -6. Clique no botão **Save** +4. Habilite o switch para **Edge Functions**. +5. Clique no botão **Save** Pronto. Você instanciou o edge firewall para sua função. @@ -345,10 +344,19 @@ Ainda na página **Edge Firewall**: 1. Selecione a aba **Rules Engine**. 2. Clique no botão **+ Rule Engine**. 3. Dê um nome fácil de lembrar à sua nova regra. -4. Selecione um *criterio (criteria)* para executar a integração. Por exemplo: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net/classes`. -5. Abaixo, selecione um *comportamento* para os *criteria*. Neste caso, será **Run Function**. Em seguida, selecione a função **Send Event to Endpoint** de acordo com o nome que você deu a ela na etapa instanciada. +4. Selecione um *criteria* (critério) para executar a integração. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Sent Event to Endpoint**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. + Pronto. Agora, a integração **Send Event to Endpoint** está sendo executada para cada requisição feita ao domínio indicado. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx index baddac9b1c..75d8e63dbb 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx @@ -76,10 +76,9 @@ Siga estes passos: 1. No canto superior esquerdo, abra o **Products menu** e selecione **Edge Firewall** na seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -4. Selecione os domínios que deseja proteger com a função. -5. Ative a opção **Edge Functions** na seção **Edge Firewall Modules**. +4. Ative a opção **Edge Functions** na seção **Edge Firewall Modules**. - Esta ação dá acesso a edge functions no edge firewall. -6. Clique no botão **Save**. +5. Clique no botão **Save**. Pronto. Agora você instanciou o edge firewall para sua função e tem acesso a edge functions em seu edge firewall. @@ -190,10 +189,17 @@ Ainda na página do **Edge Firewall**: 2. Clique no botão **+ Rule Engine**. 3. Dê um nome fácil de lembrar à sua nova regra. 4. Selecione um *criteria* (critério) para executar a integração. - - Exemplo: if `Request URI` starts with `./`. -5. Abaixo, selecione o *behavior* **Run Function** para os *criteria*. -6. Selecione a função **Upstash Waiting Room** de acordo com o nome que você deu antes. -7. Clique no botão **Save**. + - Exemplo: if `Host` *matches* `yourdomain.com`. +5. Abaixo, selecione um *behavior* (comportamento) para os *criteria* (critérios). Neste caso, será **Run Function**. + - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. +6. Clique no botão **Save**. + +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. + +7. No **Products menu**, selecione **Domains**. +8. Clique no domínio que você deseja proteger com sua função **Upstash Waiting Room**. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +10. Clique no botão **Save**. Pronto. Agora a integração **Upstash Waiting Room** está em execução. From 63dcb3ffe3b8eda57ac56a5ed6e45ca018f24ae7 Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 10:31:24 -0300 Subject: [PATCH 03/10] fix: small changes --- .../guides/marketplace/integrations/bot-manager-lite.mdx | 7 +++++++ .../marketplace/integrations/radware-bot-manager.mdx | 2 +- .../guias/marketplace/integrations/radware-bot-manager.mdx | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx index 7e372ff268..4d0b9a14fa 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx @@ -216,6 +216,13 @@ Still in the **Edge Firewall** page: 7. Select the function according to the name you gave it in step 3. 8. Click the **Save** button. +On the Console, you must now configure your domain so it is protected by your Edge Firewall. + +9. On the **Products menu**, select **Domains**. +10. Click on the domain you want to protect with your **Bot Manager Lite** function. +11. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +12. Click the **Save** button. + Done. You now have your domains protected against bot attacks by using Azion **Bot Manager Lite**. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx index ece63602ff..2a0b174d50 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx @@ -96,7 +96,7 @@ To instantiate the **Radware Bot Manager** integration, while still on the Edge 1. Select the **Functions Instances** tab. 2. Click the **+ Function Instance** button. 3. Give a name to your instance. -4. On the dropdown menu, select the **ShieldSquare Bot Manager** function. +4. On the dropdown menu, select the **Radware Bot Manager** function. - This action will load the **Arguments** tab. 5. On the **Arguments** tab, add the parameters. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx index 0c3af805a4..b3eb608f34 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx @@ -120,7 +120,7 @@ Pronto. Agora sua instância da integração **Radware Bot Manager** está salva 1. Selecione a aba **Functions**. 2. Clique no botão **Add Function**. 3. Dê um nome à sua instância. -4. No menu suspenso, selecione a função **ShieldSquare Bot Manager**. +4. No menu suspenso, selecione a função **Radware Bot Manager**. :::note Observe que o nome listado no menu suspenso é diferente do nome que está no Marketplace. From 6284da0fc3ca7e19dbec40f5383bdd5a81dc95e8 Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 10:39:18 -0300 Subject: [PATCH 04/10] fix: small changes on pt-br --- .../guides/marketplace/integrations/bot-manager-lite.mdx | 4 ++-- .../guides/marketplace/integrations/radware-bot-manager.mdx | 4 ++-- .../en/pages/guides/marketplace/integrations/waiting-room.mdx | 4 ++-- .../pages/guias/marketplace/integrations/add-request-id.mdx | 4 ++-- .../pages/guias/marketplace/integrations/bot-manager-lite.mdx | 4 ++-- .../docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx | 4 ++-- .../docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx | 4 ++-- .../pages/guias/marketplace/integrations/limit-payload.mdx | 4 ++-- .../guias/marketplace/integrations/radware-bot-manager.mdx | 4 ++-- .../marketplace/integrations/rate-limit-with-penalty.mdx | 4 ++-- .../pt-br/pages/guias/marketplace/integrations/recaptcha.mdx | 4 ++-- .../guias/marketplace/integrations/request-data-headers.mdx | 4 ++-- .../guias/marketplace/integrations/scheduled-blocking.mdx | 4 ++-- .../pages/guias/marketplace/integrations/secure-token.mdx | 4 ++-- .../guias/marketplace/integrations/send-event-endpoint.mdx | 4 ++-- .../pages/guias/marketplace/integrations/waiting-room.mdx | 4 ++-- 16 files changed, 32 insertions(+), 32 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx index 4d0b9a14fa..3c6cee67e4 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx @@ -216,11 +216,11 @@ Still in the **Edge Firewall** page: 7. Select the function according to the name you gave it in step 3. 8. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 9. On the **Products menu**, select **Domains**. 10. Click on the domain you want to protect with your **Bot Manager Lite** function. -11. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +11. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 12. Click the **Save** button. Done. You now have your domains protected against bot attacks by using Azion **Bot Manager Lite**. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx index 2a0b174d50..4cd695eae1 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx @@ -168,11 +168,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Radware Bot Manager function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the **Radware Bot Manager** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx index 8f003918ac..1711fc4932 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx @@ -193,11 +193,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Upstash Waiting Room function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the **Upstash Waiting Room** integration is running. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx index 607433fa2b..692e84bd05 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/add-request-id.mdx @@ -159,11 +159,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Add Request ID**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Você agora configurou a integração **Add Request ID** e começará a receber o cabeçalho. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx index dbfca26bf3..f026da0825 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/bot-manager-lite.mdx @@ -217,11 +217,11 @@ Ainda na página **Edge Firewall**: 7. Selecione a função de acordo com o nome que você deu no passo 3. 8. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 9. No **Products menu**, selecione **Domains**. 10. Clique no domínio que você deseja proteger com sua função **Bot Manager Lite**. -11. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +11. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 12. Clique no botão **Save**. Pronto. Agora você tem seus domínios protegidos contra ataques de bot usando a integração Azion **Bot Manager Lite**. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx index fcb959bf9d..3d2a4d8566 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/ipqs.mdx @@ -210,11 +210,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **IP Address Reputation**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora, a integração está em execução para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx index f419ad8581..18fcfbec8d 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/jwt.mdx @@ -164,11 +164,11 @@ Para isso, ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **JWT**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora você tem uma integração **JWT** rodando na sua aplicação para cada requisição que for feita ao seu domínio. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx index a72d77ca21..cee0c4ad4f 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/limit-payload.mdx @@ -171,11 +171,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Limit Payload Size**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora a integração está sendo executada para cada request feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx index b3eb608f34..037df9cc84 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/radware-bot-manager.mdx @@ -166,11 +166,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Radware Bot Manager**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora a integração **Radware Bot Manager** está em execução para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx index 4db3a13192..a7890f8992 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/rate-limit-with-penalty.mdx @@ -322,11 +322,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Upstash Rate Limiting**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora, **Upstash Rate Limiting** está em execução e protegendo seus domínios. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx index d32c4be740..76034ffa5d 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/recaptcha.mdx @@ -245,11 +245,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **reCAPTCHA**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora a integração **reCAPTCHA** está em execução para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx index 3b97066e8e..3927e64a86 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/request-data-headers.mdx @@ -157,11 +157,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Process Request Data Into Headers**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora a integração está sendo executada para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx index f41ee866b5..673849f1d3 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/scheduled-blocking.mdx @@ -289,11 +289,11 @@ Ainda na página **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Scheduled Blocking**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora, a integração **Scheduled Blocking** está em execução para cada requisição feita ao domínio que você indicou. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx index 3994803a6a..98f66b1a35 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/secure-token.mdx @@ -191,11 +191,11 @@ Ainda na página **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Secure Token**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. :::note diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx index 502937950a..8d4d304788 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/send-event-endpoint.mdx @@ -350,11 +350,11 @@ Ainda na página **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Sent Event to Endpoint**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora, a integração **Send Event to Endpoint** está sendo executada para cada requisição feita ao domínio indicado. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx index 75d8e63dbb..9648249ac6 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx @@ -194,11 +194,11 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 6. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função **Upstash Waiting Room**. -9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o Edge Firewall que você acabou de criar. +9. Na seção **Settings**, clique no seletor de `Edge Firewall` e escolha o edge firewall que você acabou de criar. 10. Clique no botão **Save**. Pronto. Agora a integração **Upstash Waiting Room** está em execução. From c11272ef454a8e241c640755e3d36acd90d39545 Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 10:43:35 -0300 Subject: [PATCH 05/10] fix: small changes on english files --- .../pages/guides/marketplace/integrations/add-request-id.mdx | 4 ++-- .../en/pages/guides/marketplace/integrations/hcaptcha.mdx | 4 ++-- .../docs/en/pages/guides/marketplace/integrations/ipqs.mdx | 4 ++-- .../docs/en/pages/guides/marketplace/integrations/jwt.mdx | 4 ++-- .../pages/guides/marketplace/integrations/limit-payload.mdx | 4 ++-- .../marketplace/integrations/rate-limiting-with-penalty.mdx | 4 ++-- .../en/pages/guides/marketplace/integrations/recaptcha.mdx | 4 ++-- .../marketplace/integrations/request-data-into-header.mdx | 4 ++-- .../guides/marketplace/integrations/scheduled-blocking.mdx | 4 ++-- .../en/pages/guides/marketplace/integrations/secure-token.mdx | 4 ++-- .../guides/marketplace/integrations/send-event-endpoint.mdx | 4 ++-- 11 files changed, 22 insertions(+), 22 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx index 9a4d216698..43047019ca 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx @@ -159,11 +159,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Add Request ID function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. You've now configured the **Add Request ID** integration and will start receiving the header. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx index 57c8bee9e8..5db98cf6b9 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx @@ -246,11 +246,11 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your hCaptcha function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx index 680a21b57e..2e4b7d02a3 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx @@ -208,11 +208,11 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your IP Address Reputation function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the IP Address Reputation integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx index a4891ca502..c41ba88faa 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx @@ -164,11 +164,11 @@ To do so, still on the **Edge Firewall** page, follow these steps: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your JWT function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now you have a JWT integration running for every request made to the domain you indicate. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx index ecd391e3a2..9af58214e7 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx @@ -170,11 +170,11 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Limit Payload Size function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the Limit Payload Size integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx index ac47dc25d9..1cc3d45c4b 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx @@ -321,11 +321,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Upstash Rate Limiting function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now **Upstash Rate Limiting** is running and protecting your domains. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx index bd89c69dfd..7819f7217e 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx @@ -243,11 +243,11 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your reCAPTCHA function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the **reCAPTCHA** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx index 22983d9f61..acdf282b32 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx @@ -157,11 +157,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your IP Process Request Data Into Header. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the **Process Request Data Into Header** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx index af173a0315..f2b595868c 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx @@ -285,11 +285,11 @@ Still in the **Edge Firewall** page. - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Scheduled Blocking function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the Scheduled Blocking integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index 74172d7fac..753effe225 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -191,11 +191,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Secure Token function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. :::note diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx index ee690fbd75..01ff4a2b44 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx @@ -350,11 +350,11 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your Edge Firewall. +On the Console, you must now configure your domain so it is protected by your edge firewall. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Send Event to Endpoint function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the Edge Firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. 10. Click the **Save** button. Done. Now the **Send Event to Endpoint** integration is running for every request made to the domain you indicated. From 2c3c231a7c6b0a57737e78d9bfc6b8a64d1f5183 Mon Sep 17 00:00:00 2001 From: Guilherme Afonso Oliveira Date: Mon, 23 Dec 2024 10:47:00 -0300 Subject: [PATCH 06/10] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Mariana Bellorín Aguilera <89138244+MarianaAguilera@users.noreply.github.com> --- .../marketplace/integrations/rate-limiting-with-penalty.mdx | 2 +- .../en/pages/guides/marketplace/integrations/secure-token.mdx | 2 +- .../pt-br/pages/guias/marketplace/integrations/waiting-room.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx index 1cc3d45c4b..f27a6cf8d8 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx @@ -347,4 +347,4 @@ Done. Now **Upstash Rate Limiting** is running and protecting your domains. Discover how to enhance your web application's performance with this tutorial on **Rate Limit with Penalty on Azion + Upstash DB**. Watch now on Azion's YouTube channel. - + diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index 753effe225..b74da34d94 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -188,7 +188,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. On the Console, you must now configure your domain so it is protected by your edge firewall. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx index 9648249ac6..72e351b2cc 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/waiting-room.mdx @@ -76,7 +76,7 @@ Siga estes passos: 1. No canto superior esquerdo, abra o **Products menu** e selecione **Edge Firewall** na seção **Secure**. 2. Clique no botão **+ Edge Firewall**. 3. Dê um nome fácil de lembrar ao seu edge firewall. -4. Ative a opção **Edge Functions** na seção **Edge Firewall Modules**. +4. Ative a opção **Edge Functions** na seção **Modules**. - Esta ação dá acesso a edge functions no edge firewall. 5. Clique no botão **Save**. From 7bce6cff2cd02ec66494ca65789f6dc7d711ac8c Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 13:57:02 -0300 Subject: [PATCH 07/10] fix: style change --- .../en/pages/guides/marketplace/integrations/add-request-id.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/ipqs.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/jwt.mdx | 2 +- .../en/pages/guides/marketplace/integrations/limit-payload.mdx | 2 +- .../marketplace/integrations/rate-limiting-with-penalty.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/recaptcha.mdx | 2 +- .../marketplace/integrations/request-data-into-header.mdx | 2 +- .../guides/marketplace/integrations/scheduled-blocking.mdx | 2 +- .../en/pages/guides/marketplace/integrations/secure-token.mdx | 2 +- .../guides/marketplace/integrations/send-event-endpoint.mdx | 2 +- .../en/pages/guides/marketplace/integrations/waiting-room.mdx | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx index 43047019ca..1cfe4a3ca1 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx @@ -159,7 +159,7 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Add Request ID function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx index 5db98cf6b9..23999f9e38 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx @@ -246,7 +246,7 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your hCaptcha function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx index 2e4b7d02a3..fdded45a4f 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx @@ -208,7 +208,7 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your IP Address Reputation function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx index c41ba88faa..1d308264e5 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx @@ -164,7 +164,7 @@ To do so, still on the **Edge Firewall** page, follow these steps: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your JWT function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx index 9af58214e7..8b66452a4d 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx @@ -170,7 +170,7 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Limit Payload Size function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx index f27a6cf8d8..560c9362d6 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx @@ -321,7 +321,7 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Upstash Rate Limiting function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx index 7819f7217e..7d2a477851 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx @@ -243,7 +243,7 @@ Still on the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your reCAPTCHA function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx index acdf282b32..baf2cf1aa6 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx @@ -157,7 +157,7 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your IP Process Request Data Into Header. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx index f2b595868c..34abb97654 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx @@ -285,7 +285,7 @@ Still in the **Edge Firewall** page. - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Scheduled Blocking function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index b74da34d94..b8ae4c8e8c 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -191,7 +191,7 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Secure Token function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx index 01ff4a2b44..79de31f549 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx @@ -350,7 +350,7 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Send Event to Endpoint function. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx index 1711fc4932..ac00a0949c 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx @@ -193,7 +193,7 @@ Still in the **Edge Firewall** page: - Select the adequate function according to the name you gave it in the instantiate step. 6. Click the **Save** button. -On the Console, you must now configure your domain so it is protected by your edge firewall. +On the Console, you must now configure your domain so your edge firewall protects it. 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Upstash Waiting Room function. From 84a0b7eba12c417a3d00663c914e160eb9f4b435 Mon Sep 17 00:00:00 2001 From: Guilherme Afonso Oliveira Date: Mon, 23 Dec 2024 15:00:26 -0300 Subject: [PATCH 08/10] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Mariana Bellorín Aguilera <89138244+MarianaAguilera@users.noreply.github.com> --- .../pages/guides/marketplace/integrations/bot-manager-lite.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/ipqs.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/jwt.mdx | 2 +- .../en/pages/guides/marketplace/integrations/limit-payload.mdx | 2 +- .../guides/marketplace/integrations/radware-bot-manager.mdx | 2 +- .../marketplace/integrations/rate-limiting-with-penalty.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/recaptcha.mdx | 2 +- .../marketplace/integrations/request-data-into-header.mdx | 2 +- .../guides/marketplace/integrations/scheduled-blocking.mdx | 2 +- .../en/pages/guides/marketplace/integrations/secure-token.mdx | 2 +- .../guides/marketplace/integrations/send-event-endpoint.mdx | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx index 3c6cee67e4..a7fc23ea55 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/bot-manager-lite.mdx @@ -213,7 +213,7 @@ Still in the **Edge Firewall** page: 5. You have to create additional *criteria* for this integration to work: `if Request URI does not match /.well-know/` - This rule is highly recommended to create a list of allowed IPs that don't impact automation or scripts to WEB API. 6. Below, select **Run Function** *behavior*. -7. Select the function according to the name you gave it in step 3. +7. Select the adequate function according to the name you gave it during the instantiation step. 8. Click the **Save** button. On the Console, you must now configure your domain so it is protected by your edge firewall. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx index 23999f9e38..332ddfbb42 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx @@ -243,7 +243,7 @@ Still on the **Edge Firewall** page: 3. Give a name to the rule. 4. Select a criteria to run and catch the domain you want to run the integration on. Example: `if Hostname is equal xxxxxxxxxxxx.map.azionedge.net`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx index fdded45a4f..6dc03b4653 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx @@ -205,7 +205,7 @@ Still on the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx index 1d308264e5..50b5d4073d 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx @@ -161,7 +161,7 @@ To do so, still on the **Edge Firewall** page, follow these steps: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx index 8b66452a4d..00628dfffa 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx @@ -167,7 +167,7 @@ Still on the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx index 4cd695eae1..880814f739 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/radware-bot-manager.mdx @@ -165,7 +165,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so it is protected by your edge firewall. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx index 560c9362d6..d744e1cc74 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx @@ -318,7 +318,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx index 7d2a477851..570c666c7c 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx @@ -240,7 +240,7 @@ Still on the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx index baf2cf1aa6..ea88ddb27e 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx @@ -154,7 +154,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx index 34abb97654..f730e0f0a8 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx @@ -282,7 +282,7 @@ Still in the **Edge Firewall** page. 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index b8ae4c8e8c..5561ec6fe5 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -188,7 +188,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx index 79de31f549..3db21f89b5 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx @@ -347,7 +347,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it. From d0e30002191871e8caf4940796f2d1fc68e7c83b Mon Sep 17 00:00:00 2001 From: guiafonso-ol Date: Mon, 23 Dec 2024 19:24:54 -0300 Subject: [PATCH 09/10] fix: small style changes --- .../en/pages/guides/marketplace/integrations/add-request-id.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/ipqs.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/jwt.mdx | 2 +- .../en/pages/guides/marketplace/integrations/limit-payload.mdx | 2 +- .../marketplace/integrations/rate-limiting-with-penalty.mdx | 2 +- .../docs/en/pages/guides/marketplace/integrations/recaptcha.mdx | 2 +- .../marketplace/integrations/request-data-into-header.mdx | 2 +- .../guides/marketplace/integrations/scheduled-blocking.mdx | 2 +- .../en/pages/guides/marketplace/integrations/secure-token.mdx | 2 +- .../guides/marketplace/integrations/send-event-endpoint.mdx | 2 +- .../en/pages/guides/marketplace/integrations/waiting-room.mdx | 2 +- .../pt-br/pages/guias/marketplace/integrations/hcaptcha.mdx | 2 +- 13 files changed, 13 insertions(+), 13 deletions(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx index 1cfe4a3ca1..e8f6cc6d56 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx @@ -163,7 +163,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Add Request ID function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. You've now configured the **Add Request ID** integration and will start receiving the header. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx index 332ddfbb42..7ac267023d 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/hcaptcha.mdx @@ -250,7 +250,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your hCaptcha function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx index 6dc03b4653..4a59a3bbdd 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/ipqs.mdx @@ -212,7 +212,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your IP Address Reputation function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the IP Address Reputation integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx index 50b5d4073d..149d4a62f3 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx @@ -168,7 +168,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your JWT function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now you have a JWT integration running for every request made to the domain you indicate. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx index 00628dfffa..8e23e8d244 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx @@ -174,7 +174,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Limit Payload Size function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the Limit Payload Size integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx index d744e1cc74..308c2bcdd1 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/rate-limiting-with-penalty.mdx @@ -325,7 +325,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Upstash Rate Limiting function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now **Upstash Rate Limiting** is running and protecting your domains. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx index 570c666c7c..a84fac0842 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/recaptcha.mdx @@ -247,7 +247,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your reCAPTCHA function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the **reCAPTCHA** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx index ea88ddb27e..4c92128dd6 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx @@ -161,7 +161,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your IP Process Request Data Into Header. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the **Process Request Data Into Header** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx index f730e0f0a8..5f2452e910 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx @@ -289,7 +289,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Scheduled Blocking function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the Scheduled Blocking integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index 5561ec6fe5..b3e4b02d03 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -195,7 +195,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Secure Token function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. :::note diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx index 3db21f89b5..cf713f0c9d 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/send-event-endpoint.mdx @@ -354,7 +354,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Send Event to Endpoint function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the **Send Event to Endpoint** integration is running for every request made to the domain you indicated. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx index ac00a0949c..7d495c6be3 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/waiting-room.mdx @@ -197,7 +197,7 @@ On the Console, you must now configure your domain so your edge firewall protect 7. On the **Products menu**, select **Domains**. 8. Click on the domain you want to protect with your Upstash Waiting Room function. -9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you've just created. +9. In the **Settings** section, click on the `Edge Firewall` selector and choose the edge firewall you created. 10. Click the **Save** button. Done. Now the **Upstash Waiting Room** integration is running. diff --git a/src/content/docs/pt-br/pages/guias/marketplace/integrations/hcaptcha.mdx b/src/content/docs/pt-br/pages/guias/marketplace/integrations/hcaptcha.mdx index 24cf083f4f..168c636cd3 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/integrations/hcaptcha.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/integrations/hcaptcha.mdx @@ -246,7 +246,7 @@ Ainda na página do **Edge Firewall**: - Selecione a função adequada de acordo com o nome que você deu na etapa de instanciação. 5. Clique no botão **Save**. -Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu Edge Firewall. +Agora, no Console, você deve configurar seu domínio para que ele seja protegido pelo seu edge firewall. 7. No **Products menu**, selecione **Domains**. 8. Clique no domínio que você deseja proteger com sua função hCaptcha. From 041759d00a2119b9e44fb95679579c4fc4685162 Mon Sep 17 00:00:00 2001 From: Guilherme Afonso Oliveira Date: Tue, 24 Dec 2024 09:36:33 -0300 Subject: [PATCH 10/10] Update src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Mariana Bellorín Aguilera <89138244+MarianaAguilera@users.noreply.github.com> --- .../en/pages/guides/marketplace/integrations/add-request-id.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx index e8f6cc6d56..20ca1e98f2 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/add-request-id.mdx @@ -156,7 +156,7 @@ Still in the **Edge Firewall** page: 4. Select a *criteria* to run and catch the domains that you want to run the integration on. - Example: if `Host` *matches* `yourdomain.com`. 5. Below, select a *behavior* to the *criteria*. In this case, it'll be **Run Function**. - - Select the adequate function according to the name you gave it in the instantiate step. + - Select the adequate function according to the name you gave it during the instantiation step. 6. Click the **Save** button. On the Console, you must now configure your domain so your edge firewall protects it.