Skip to main content
Open console

The edge

What the proxy in front of every environment refuses on its own, what you can switch on, and how to take a site offline.

14 min read

Every request to your site passes through a proxy on the machine, which terminates HTTPS, routes the hostname to the right environment and applies the rules below. The platform's rules apply to everyone; yours are set on the project's Edge tab and each environment's Routing tab.

All of it is the Basic WAF and bot management add-on, included on every project at no cost and shown on your invoice at nothing. It covers what is refused below, SQL injection counted or refused, and every request named by the kind of client that sent it.

In order

A request meets the checks in this order. The first one that refuses it answers.

  1. HTTPS. Plain HTTP is redirected to HTTPS; see Domains.
  2. Probe guard: the platform's rules, what is refused by default for your kind of project, and your own probe rules.
  3. Blocked addresses, allowed addresses and blocked user agents.
  4. Password protection.
  5. Rate limit.
  6. Compression and HSTS, on the way back out.
  7. The redirect to your primary domain: from the platform hostname once one of your own is primary, and from every other hostname once it is canonical.

What is refused for everyone

The probe guard refuses requests for files no site should serve, before they reach your application:

  • hidden files
  • paths that try to climb out of the web root
  • the well-known names of configuration and credential files, and backup copies of those

/.well-known/ is the exception. Matching ignores case.

A refused request gets a 404, not a 403. The probe guard does not stop an attack on a URL your application really serves.

You cannot turn it off or change what it covers. If it refuses a path your application needs, tell us. To add to it, write your own probe rules.

Refused by default

Three more refusals depend on what your project is. Each is on unless you turn it off on the project's Edge tab. A refused request gets a 404 and your probe page. They apply on shared machines too, where your other proxy options do not.

Refused Where What it covers
Requests with no user agent Every project A request that names no user agent at all. Every browser, crawler, HTTP library (curl, Python's requests, Go, Node's fetch) and payment or Git webhook sends one
WordPress paths Projects that are not WordPress /xmlrpc.php; anything under /wp-admin, /wp-includes, /wp-json, /wp-content/plugins, /wp-content/themes and /wp-content/mu-plugins; wp-*.php anywhere (wp-login.php, wp-cron.php); /wp-admin/ and /wp-includes/ under a subdirectory; code files (.php, .phtml, .phar) under /wp-content/; and PHPUnit's vendor/phpunit/ and eval-stdin.php
.php Projects that run Node.js, Go, Python, Ruby or Rust, and static sites A .php, .phtml or .phar file anywhere in the path, /index.php/admin included

Not refused: /wp-content/uploads/, /vendor/ as a whole, /config.json and /robots.txt.

SQL injection

On the project's Edge tab, under Refused by default, choose what the probe guard does with SQL injection in the address:

Setting What happens
Count only The default. The request reaches your site, and the Metrics tab says how many carried it
Refuse Answered as a probe, a 404 with your probe page, and counted as refused
Off Neither

It knows the shapes a scanner tries (UNION SELECT, ' OR 1=1, SLEEP(5), ; DROP TABLE) in the path and the query string, never in what a form posts.

Count first and look at what was counted: if it is all scanners, refuse. It stops a scanner working through its list, not somebody who has studied your site. Queries with bound parameters are what keep a database safe.

Test a path on the Edge tab says when one of these is what refuses a path, and which switch to turn off. Turn one off if a client of yours calls your site without a user agent, or if your site serves a path from the list.

Your own probe rules

On the project's Edge tab, under Probe rules, list paths your site never serves. They are refused like the platform's, with a 404 and your probe page, on every environment, after the platform's own rules.

Kind Example Matches
Exact paths /xmlrpc.php That path, ignoring case and a trailing slash
Path prefixes /old-admin/ Everything beneath it, ignoring case
Globs *.bak, /wp-json/*/users * within one segment, ** across segments, ? one character, ignoring case. Without a slash it matches the last segment at any depth; with one, the whole path from the start
Patterns ^/api/v[0-9]+/debug A regular expression in RE2 syntax, anywhere in the path unless anchored, case-sensitive unless you add (?i)

One rule per line, at most 50 in all, each up to 200 characters. Refused: a rule that would refuse your home page, and the pattern features RE2 lacks (look-ahead, look-behind, back-references).

A rule broader than you meant refuses pages your visitors want, with a 404 that looks like a missing page. Test a few real paths of your own site afterwards. Test a path, under the rules, says which rule would refuse a path, yours or the platform's, against the rules as saved.

Rules worth having:

Kind Rule Refuses
Exact path /xmlrpc.php WordPress's XML-RPC endpoint, on a site that does not publish from an app
Exact path /user/register Drupal's sign-up form, on a site where nobody signs up
Path prefix /old-admin/ An admin area you moved
Path prefix /wp-json/wp/v2/users WordPress's user list, which hands out login names
Glob *.bak, *.old, *.orig Backup copies of any file, at any depth
Glob *.sql, *.sql.gz, *.zip Database dumps and archives left in the web root
Glob /wp-content/uploads/**/*.php A PHP file in uploads
Pattern ^/api/v[0-9]+/debug A debugging route in every API version
Pattern (?i)/(phpmyadmin|pma|adminer) Database tools that are not installed, at any depth

A machine needs agent 0.5.136 or later to apply them. It upgrades on its own; until then the tab names it and it keeps the platform's rules alone.

Your rules

Set on What Applies to
The project's Edge tab Blocked addresses, blocked user agents, rate limit, compression, hiding application errors, HSTS, your own probe rules, and the pages the edge serves in place of your site Every environment of the project
An environment's Routing tab Allowed addresses, restricted paths, password protection, keeping a visitor on one machine That environment

The Edge tab is one form with one Save. The options and the pages are checked together, and if anything is refused nothing is kept.

Not on shared infrastructure. On a machine the platform shares between customers, none of these apply: neither the project's options nor an environment's own. The Edge tab names any environment they skip, and an environment's Routing tab says so. Your own machines, dedicated or shared between your own environments, have them all. The pages the edge serves apply everywhere.

Allowed and blocked addresses

One address or range per line, IPv4 or IPv6.

  • Allowed addresses, per environment: when there are any, only those can reach the environment. Empty means everyone. Our uptime checks are always let in as well, so a restricted site is still measured rather than reported down.
  • Blocked addresses, for the whole project: refused on every environment, even if its allow list permits them.

A refused visitor gets a 403.

# Allowed addresses on staging: the office, and the VPN everybody else uses
203.0.113.0/24
198.51.100.14

# Blocked addresses on the project: a scraper's network, IPv4 and IPv6
192.0.2.0/24
2001:db8:42::/48

Behind the platform's CDN, its copies answer first. A page the CDN already holds is served to whoever asks, without reaching the environment. To keep a page to the list, name it under Never cache these paths on the CDN tab, or have your application send Cache-Control: private. Restricted paths are marked private for you.

Behind a CDN, the address is the one the CDN reports: the platform CDN's, or the header of the network you named on your domain. It is believed only on requests from that CDN's published edge addresses. Anything connecting directly is judged by its own address, so the header cannot be forged past the rules.

Behind a CDN that publishes no edge addresses, a block list stops nobody and an allow list stops everybody. That is Akamai, or a CDN the platform has no entry for: the header is never believed. Domains has the details.

Restricted paths

Under Restricted access on the environment's Routing tab, fill in two lists: the paths, and the addresses that may reach them. Everybody else is refused with a 403 on those paths, and only on those.

  • Each path covers everything under it. /admin covers /admin and /admin/people, not /administration. There are no wildcards.
  • A path matches however it is spelled: in any case, with doubled slashes, with . and .. resolved, with an encoded slash read as a slash, and through /index.php. /index.php/admin is Drupal's /admin.
  • ! exempts a path under one. Restricting /wp-admin without exempting /wp-admin/admin-ajax.php breaks forms and carts: WordPress's public pages call it for every visitor.
# Restricted paths on a WordPress production site
/wp-admin
!/wp-admin/admin-ajax.php
/wp-login.php

# Addresses for restricted paths: the office, and the VPN
203.0.113.0/24
198.51.100.14

Restricted paths are checked after blocked and allowed addresses:

  • An address blocked for the project stays blocked here.
  • Where the environment has allowed addresses, the ones for a restricted path have to be among them.

Behind a CDN, the address is the one the CDN reports. What a restricted path answers is marked Cache-Control: private, so the CDN never keeps a copy of it.

A path nobody may reach at all is a probe rule. Restricting / restricts the whole site: use allowed addresses for that.

Blocked user agents

One per line, matched anywhere in the user agent, ignoring case: GPTBot is enough. A match gets the same 403.

Blocking Googlebot and bingbot takes your site out of the search results.

# Crawlers gathering text to train language models
GPTBot
ClaudeBot
CCBot
Bytespider
meta-externalagent

# SEO tools crawling for somebody else's report
AhrefsBot
SemrushBot
MJ12bot

This is for crawlers that name themselves honestly. Scanners send an ordinary browser's user agent: use the probe guard and the address lists for them.

Password protection

One user:hash per line, the format htpasswd writes:

htpasswd -nB reviewer

It asks for the password, then prints the line that goes in the box:

reviewer:$2y$05$4kcvXm6qX1xJt8Lr2dYQ3e7oQ0Sx9uM3cB1tFhZ5u3pQe6rA2wC1y
  • A plain password is refused: everyone who can open the Routing tab could read it.
  • Use -B (bcrypt). The form accepts some older hash formats as well, but bcrypt is the one to rely on.
  • Add one line per person who reviews the site, so you can take one away without telling everybody a new password.
  • It covers every hostname of the environment, the platform hostname at vallic.cloud included.
  • Two things pass without it: the challenge a certificate authority uses to issue your certificate, and the platform's own health check.
  • Our uptime checks are asked for the password like everybody else, and count being asked as the site answering. Whether the application itself is up is read from the health check, which the password does not cover.

Rate limit

Requests per second is what a single visitor can average. Burst is how far it may go over that for a moment. Zero means no limit; a burst left at zero is the same as the rate. A client over the limit is answered 429 Too Many Requests until it slows down.

The limit is set once for the project and counted on each environment separately: requests to staging do not use up a visitor's allowance on production.

Starting points, to watch and adjust:

Site Requests per second Burst
A brochure site or a blog 10 50
A shop, behind a CDN that serves the images 15 40
An API that apps call 5 10

A visitor loading a page that pulls thirty images and scripts from your origin needs a burst of thirty to see it whole.

Whose address is counted depends on what is in front of the site:

  • Nothing: the address that connects.
  • Our CDN, Cloudflare or Fastly: the visitor address the CDN reports, believed only from that CDN's own edge servers.
  • Any other CDN: the limit counts per CDN edge server, so everyone that server carries shares the budget. The page says so when it applies. Set the limit with that in mind, or leave rate limiting to the CDN.

Compression

Compress responses has the proxy compress what your application sends with gzip, Brotli or zstd, whichever the browser asks for. It is on unless you turn it off. A response your application or a CDN already compressed is passed on as it is.

Application errors

Hide application errors is on for every project. When your application answers with a 500, visitors see the platform's error page in its place, still with the 500 code. A stack trace, a database query or a file path in your error output never reaches them. Your application's own log keeps the error as it was.

Turn it off where visitors should see your own 500 page, or where you are reading debug output on staging. It applies to every environment of the project, on shared machines too.

HSTS

HSTS max-age, in seconds tells browsers to refuse plain HTTP for your site for that long. Zero, the default, does not send the header.

A value set by mistake outlives the mistake: browsers remember it. Raise it once you are sure:

Value For
300 Five minutes: trying it out, on a site you can afford to be wrong about
604800 A week: the first real step
31536000 A year: once every hostname of every environment has served HTTPS for a while

The header is sent without includeSubDomains or preload, and there is no setting for either.

Keeping a visitor on one machine

Only offered where an environment answers from more than one web machine. It is for an application that keeps sessions on local disk and cannot move them. It costs you some of what the second machine was for: see the note on the form.

Taking a site offline

On the environment's Routing tab, turn on Show the offline page instead of the site. It needs the Admin role.

  • Visitors get a 503 with a Retry-After, which tells search engines the outage is temporary.
  • You can add a one-line note for visitors.
  • The site keeps running behind it. Deploys, the shell and restores all still work, so use it for a large migration, a restore or a content freeze.
  • There is no bypass: no address, cookie or hostname sees the site while it is offline. Check your work on staging, or turn the page off again to look.

Deploys do not use it: a deploy never takes your site offline on its own.

Your own pages

On the project's Edge tab, under Pages the edge serves, write what a visitor sees when the edge answers instead of your site:

Code When
503 The site is offline or being deployed
403 A request is blocked
404 A request is refused as a probe
502 Your application does not answer
504 Your application answers too slowly
500 In place of your application's own error, while application errors are hidden

Leave one empty and visitors get the platform's page, which is branded Vallic.

  • Each page is complete HTML, served as written.
  • It must not load anything from the site it stands in for, which is unreachable: inline the styles and embed any image.
  • Each has a size limit, and the form says which is too large.
  • The form lists the placeholders each page can use, such as the time and the region, and links to the platform's own page for comparison.

When your application is not answering

If your application returns a 502, 503 or 504, or does not answer at all, visitors get the platform's page or your own page instead of its response. That includes a 503 your application sends deliberately: its own maintenance page is replaced.

A 500 is replaced too while application errors are hidden, which they are unless you turn that off.

When a change takes effect

Saving sends the change to every machine the environment runs on, which picks it up within about a minute. Nothing restarts, and the proxy reloads without dropping connections. That applies to the project's Edge tab, an environment's Routing tab, and taking a site offline.

Who can do what

Role needed
The project's Edge tab: blocks, rate limit, compression, HSTS, probe rules, pages Admin
An environment's own: allowed addresses, password, one machine per visitor Developer; Owner on production
Taking the site offline Admin

See Teams.

Next

  • Domains — the hostnames these rules apply to
  • CDN — caching and blocking by country, further out