Copy an HTTP Application
Copy an existing HTTP application when you need a new application with the same configuration but different domains, ports, or gateway partitions. The source application is never modified.
This feature was first introduced in OpenResty Edge 26.9.1-1.
Start a copy
Users with application write permission can select Copy from the HTTP application list or the application header. Only HTTP applications can be copied.
Configure the destination with its domains and the source-to-destination domain mapping, its gateway partitions, its HTTP and HTTPS ports, and the modules to copy. At least one HTTP or HTTPS port is required, and every source domain must map to a destination domain. Where copied configuration refers to a source domain, the first destination domain becomes the default domain.
Select modules
The copy workflow covers origin clusters and nodes, Kubernetes upstreams, request and response rewrite rules, cache purge rules and cache warmup tasks, WAF allowlists, IP lists and authentication lists, ClientHello rules, custom variables, and SSL certificates only when you select them explicitly. Everything except SSL certificates is selected by default.
Runtime cache-warmup progress and logs are not copied, and neither are application user ACLs, tests, or any other unsupported section.
Handle certificates safely
Copying an SSL certificate copies its private key as well. Leave certificates unselected unless the same key is intentionally authorized for the destination; in most cases, issue a new certificate whose SANs match the destination domains.
Complete and release
A successful copy creates new resource IDs and opens the destination application. Review its domains, upstreams, security rules, certificates, and partitions. The copied configuration is saved in Edge Admin, but it does not reach gateway nodes until you release it.
If the copy fails, correct the domain mapping, port selection, permission, or referenced-resource error and retry. A failed copy leaves the source untouched.