Basic Configuration

The Basic Configuration page is where you set up the foundation of your site — routing traffic to your origin server, managing hostnames, and configuring core settings that other features build on.

---

Origin / Load Balancer

Every site needs a destination for traffic. In the Basic Configuration, you assign either a single origin server or a load balancer that distributes traffic across multiple origins.

1. Navigate to your Site in smoxy

2. Open Basic Configuration

3. Select your origin or load balancer from the dropdown

This determines where smoxy sends requests by default. You can override this per-request using Conditional Rules.

Note: Origins and load balancers are created separately under Organization > Origins & Loadbalancer before they can be assigned to a site.

---

Hostnames

The Basic Configuration page shows all hostnames (domains) linked to your site. You can:

• Add new hostnames to the site

• View configuration status (e.g., missing CNAME records)

• Move a hostname to a different site

• Remove a hostname from the site

• Access DNS & SSL settings for each hostname

When you add a hostname, it immediately inherits all of the site's configuration settings.

---

Enable smoxy

The Enable smoxy toggle activates the full smoxy feature set (caching, optimization, security, rules) for this site. When disabled, smoxy acts as a simple reverse proxy without any optimization or caching.

This must be enabled before features like caching, image optimization, acceleration, or security can be used.

---

Cache Token

The cache token is used to authenticate requests to the cache invalidation API. Set a token here and include it in your purge requests to authorize cache clearing operations.

---

Debug Headers

When enabled, smoxy adds debug information to HTTP response headers. This is useful for troubleshooting caching behavior, rule evaluation, and request routing.

Enable this during development or debugging, and disable it in production to avoid exposing internal details.

---

SSI & ESI

smoxy supports Server Side Includes (SSI) and Edge Side Includes (ESI) for assembling pages from multiple fragments at the edge.

Feature	Description
SSI	Process <!--#include --> directives in HTML responses
ESI	Process <esi:include> tags for edge-side page assembly

Note: ESI can only be enabled when SSI is also enabled.

These features are useful for sites that compose pages from cacheable fragments with different TTLs (e.g., a static header cached for hours and a dynamic cart widget cached for seconds).

---

HTTP Headers

You can add custom HTTP headers that smoxy includes on every request or response for this site.

Request Headers

Headers sent from smoxy to your origin server. Useful for passing additional context to your backend.

Format: One header per line as header-name = value

Response Headers

Headers sent from smoxy to the visitor's browser. Useful for security headers, CORS, or custom metadata.

Format: One header per line as header-name = value

Headers configured here apply to all requests on this site. To set headers conditionally (e.g., only for specific paths or countries), use Conditional Rules.

---

For caching, security, image optimization and custom pages settings, see the respective feature documentation pages.