Configuration Modules

These are some of the configuration modules available in the Web Accelerator.

Distinction between Mobile/Desktop Browsers

The Web Accelerator can be configured to cache pages requested by desktop and mobile browsers separately. This allows for caching even outdated sites that use server-side browser sniffing.

If the backend issues a Vary header that prevents caching, the Web Accelerator can rewrite it.

Blocking Undesirable Clients

The module examines the User-Agent header to block certain types of scans or aggressive crawlers that do not add value to the site.

It is reasonably safe to use because the same configuration protects over 100,000 Seeweb client sites.

It is possible to manipulate cookies directed to the backend to eliminate those that would prevent caching.

Edge Side Includes (ESI)

The Web Accelerator can use a simple markup language to compose a page from multiple requests made to the backend. In this way, a single page can be composed of elements that can be cached and others that are dynamic.

Geoblocking or Geoallowing

It is possible to block requests from certain countries or accept them only from those listed.

Prevent Hotlinking

This module prevents the hotlinking of images.

WebP Handling Negotiation

Some sites implement WebP image handling through server-side negotiation to adapt to the capabilities of the visitor's browser.

A site that changes its response based on secondary characteristics of the request would not be compatible with a frontend cache, but this module solves the problem by implementing WebP negotiation directly in the Web Accelerator.

fail2ban

fail2ban can be activated on the Web Accelerator to block repetitive attacks without them reaching the backend.

It is important that it is not active on the backend, as the traffic all comes from the Web Accelerator's IP and therefore could not be blocked.