Mobility platform / Edge migration
31 hostnames. One coordinated edge migration.
3 separate systems
WAF on 4 of 31 hosts
31 hosts migrated
WAF across the estate
The constraint
Traffic was split across three systems, with WAF protection covering only four of 31 hostnames.
The engineering decision
Rebuild rules from the source export, account for first-match behaviour, and verify redirects and certificates before cutover.
Consolidated edge configuration. Certificate ready before nameserver cutover.
Discuss a similar scopeInside a cutover record
Reusable checklists for this type of work. These are blank working templates, not the client’s project records.
Edge migration behaviour checklist
Compare source and target behaviour before moving application traffic.
| Behaviour | Compare on source and target | Pass condition |
|---|---|---|
| Redirects | Status code, destination, query string handling and rule order. | Each agreed test URL returns the expected status and location. |
| Protection | Effective action, rule priority and exception scope. | Test traffic receives the intended action; authorised exceptions remain bounded. |
| Caching | Cache key, bypass conditions, expiry and invalidation. | Cacheable responses hit as expected; private responses are not cached. |
| Origin routing and TLS | Origin selection, host header, SNI and certificate validation. | The intended backend responds over the approved TLS path. |
Before you close the record
- Results reference request traces or captured headers.
- Differences are resolved or explicitly accepted by the application owner.
- Parity is checked by behaviour, not by matching rule counts.
This is a reusable migration worksheet, not a result from the case studies shown on this site.