9.1. General information about protection service

Main features

  • Protecting your site from unwanted requests:
    • Restrict access by IP address and country.
    • Check the visitor according to the selected mode.
  • Distribution of requests between servers (if there are several). The server that should process the request is selected from the list based on the specified rules.
  • Reducing the load on the server with the site by caching responses.
  • Compress responses to reduce traffic.

Suitable for protecting sites on hosting, VPS, Dedicated, and third-party hosting.

Service

Order

Simply add a site in the "Protection" section and pay for the service.

Payment

The service is activated immediately after ordering. Then you need to create an invoice and pay for it in any available way. The service is paid per period (not daily).

Delete

Unpaid service is automatically deleted after 10 days.

Only an unpaid service can be manually deleted.

Scheme of work

sequenceDiagram autonumber participant c as Client box Protection server participant pf as Filters participant pp as Protection participant pc as Cache participant pb as Balancer end participant s as Server with site c->>pf: Request pf->>pf: Checking the client IP break Access denied pf-->>c: Error 403 end pf->>pp: Request opt If protection is enabled pp->>pp: Checking the client break Check failed pp-->>c: Error 429 end end pp->>pc: Request opt If caching is enabled pc->>pc: Checking for cache opt Cache has the appropriate data pc->>c: Response from cache end end pc->>pb: Request opt If more than one server pb->>pb: Choosing a server with the site end pb->>s: Request s->>s: Request processing alt Server returned an error s->>c: Error else Server returned a response s->>pc: Response opt If compression is enabled pc->>pc: Compression end opt If caching is enabled pc->>pc: Response caching end pc->>c: Response end

  1. Request. The client accesses the site and the request goes to the protection server.
  2. Filters. The client's IP address is checked by blacklist, whitelist, and filter by country. If access is denied, error 403 is returned.
  3. Protection (if enabled). The client is checked according to the selected protection mode. If the check fails, error 429 is returned.
  4. Choosing a server. The balancer chooses which server with the site to forward the request to. If there is only one server, the balancer settings are ignored and that server is chosen.
  5. Sending the request to the server with the site.
  6. Getting a response from the server with the site.
  7. If the response is an error, it is immediately forwarded to the client.
  8. Compression (if enabled). The response is compressed to save traffic.
  9. Caching (if enabled). The response is cached to speed up subsequent similar requests and reduce the load on the server with the site.
  10. Forwarding the response to the client.

With caching enabled and appropriate data in the cache, steps 4-9 do not work.

Content
    (2)