Site settings

Open Site Settings to change a Site’s hostname, runtime, web behaviour and supported security options.

Site identity

Use Change Domain to change the Site's primary hostname without changing its Site identity. When the conventional apex/www pair is attached, choose the preferred hostname for canonical redirects.

Traffic and availability

Choose HTTP/HTTPS behaviour, ingress binding, request/upload allowance and Maintenance Mode. Dedicated catch-all ingress is intended for hostname-routing workloads that deliberately receive externally managed hostnames.

PHP runtime

PHP Sites can use managed workload profiles or a supported custom policy for memory, upload size, execution time and worker limits. Application requirements may justify a larger profile than the default.

Managed cache

Eligible PHP, Node.js and Python Sites can attach Redis. Choose Site-owned service for a cache dedicated to the Site or Legacy shared ACL for the shared Redis service. Select the hosting mode before attaching; an existing cache is not moved automatically.

Resilience

Choose whether Control automatically repairs supported configuration drift and how much repeated failure is tolerated before operator review is required.

Web Application Firewall

When ModSecurity/OWASP CRS is available, choose Off, Detection only or Block malicious requests. PL1 is the recommended starting point for ordinary applications. Higher sensitivity levels can increase false positives.

Control-owned HTTP scheduled jobs that target their own Site use the trusted local Site path, so you should not need to disable the Site WAF just to run a trusted same-Site job.

Redirects

Add exact-path redirects where required. Keep application-level routing inside the application rather than creating broad redirects in Site Settings.