Base settings

Learn how to configure the basic protection settings for your resource.

What you can configure

  • The resource name and description in the management console.

  • The application-layer DDoS protection status: turn it off or turn it back on.

  • Access to the resource for search engine crawlers.

  • The HTTP to HTTPS redirect.

  • The redirect to the domain without www.

  • The protocol used to send clean traffic to the origin.

How to configure settings

Go to Application protection → Resources. Click the ellipsis (…) next to the required resource and select Settings.

The Base settings tab opens.

The available settings may differ depending on the integration option you use.

Base settings tab

The table below describes each setting in detail.

Setting Description

Resource name

The resource name in the management console.

The field can contain your website or application domain, or any text, such as Application 1.

If it contains any text, you can change it at any time.

If it contains a resource domain, we recommend that you do not edit the field. It affects how Strictera Application protection works:

  • The system automatically protects the domain specified as the resource name: it receives traffic addressed to the domain, filters it according to the configured policies, and sends legitimate requests to your origin servers.

  • The system protects only domains specified as the resource name and/or added on the Domains & SSL tab. It drops traffic for all other domains.

If you decide to replace the domain in the Resource name field with any text, first:

  1. Open the Domains & SSL tab.

  2. In the Protected domains section, click + Add domain.

  3. Add the domain that was previously specified as the resource name.

This is necessary to keep the domain protected.

Description

Any text note that helps you find the resource in the list. For example: Company main website or Test environment.

Application-layer DDoS protection

The application-layer protection status.

If the option is enabled, application-layer protection works as follows:

  • In Anti-bot mode, the system blocks bots and DDoS attacks 24/7 and allows only legitimate requests to reach your servers.

  • In Anti-DDoS mode, the system enables filtering only during a DDoS attack. At other times, it allows all requests, including requests from bots and automation, to reach your servers.

If the option is disabled, application-layer protection does not work: the system does not enable filtering in either Anti-bot or Anti-DDoS mode.

How can I find out which mode is enabled for a resource?

Go to Application protection → Resources. You will see a list of all resources.

If Anti-bot mode is enabled for a resource, a bot icon appears next to it. If there is no icon, the resource uses Anti-DDoS mode.

Resource list

We recommend keeping the option enabled so that the resource remains protected from bots, DDoS attacks, and other unwanted traffic.

Access for search engine crawlers

Access to the resource for search engine crawlers, such as Googlebot.

If the option is enabled, protection allows search engine crawlers to index your website.

If the option is disabled, protection blocks crawlers.

We recommend keeping the option enabled if users should be able to find your resource through search engines.

HTTP to HTTPS redirect

Redirects HTTP traffic to HTTPS.

If the option is enabled, when a user tries to access your resource over HTTP (http://example.com), protection redirects them to HTTPS (https://example.com).

If the option is disabled, the HTTP to HTTPS redirect does not occur.

The option is not available in the UI for the Module integration option. In this case, configure the redirect in your infrastructure.

Proxy to origin over HTTP

Sends traffic to the origin over HTTP instead of HTTPS.

If the option is enabled, when a legitimate user sends an HTTPS request, the system decrypts it using the SSL/TLS certificate and then sends it to the origin server over HTTP.

If the option is disabled, the system sends the legitimate HTTPS request to your origin server over HTTPS.

The option is not available in the UI for the Module integration option. Configure traffic delivery to the origin in your infrastructure.

Redirect from www.<domain> → <domain>

Redirects requests to the main resource domain without www.

If the option is enabled, when a user tries to access the www subdomain of your resource (www.example.com), the system redirects them to the main domain (example.com).

If the option is disabled, the redirect to the domain without www does not occur.

The option is not available in the UI for the Module integration option. In this case, configure the redirect in your infrastructure.

For the Hybrid option, the setting applies only to HTTP traffic. This traffic arrives unencrypted, so protection can return a redirect. Configure the redirect for HTTPS traffic in your infrastructure.