A simpler path to the edge.
Connect your site. Choose what stays out of cache. Check the rules before you save.
Cache exclusions
Keep sensitive pages out of the path cache model. Start with the example store rules, then add your own.
One path per line. Literal paths or one trailing * only, such as /private/*. Case sensitive. No regex, query strings or encoded paths. Maximum 50 rules.
Connect the demo profile to review and save.
Simulated change review
Local path rules only. This is not an EdgePrizm API payload.
Saved demo readback
Try a few paths
Results use your current editor rules. “No path exclusion” means no rule matched, not proof the CDN will cache the response.
Use https://fieldwork.test with a plain path. No query string, fragment, credentials or other host.
CDN connection + exclusions
The narrow experience shown here. Live onboarding, DNS and TLS need a test customer walkthrough.
Image transformation
Keep separate until EdgePrizm confirms the available API and where transformation runs.
Security, WAF and bots
Outside this Free prototype. Product availability and API coverage need their own validation.
Run it against a real CDN test site
The page above is a simulation. Everything below is not: it drives an isolated test site on a development CDN account through a server-side adapter, with real configuration records, a real edge and real cache behaviour. It switches itself on when you open this page; the CDN credentials stay on the server and never reach this browser. A change reaches the edge two to three minutes later, and the gateway cannot update an existing record, so changing one means replacing it; pressing apply again is safe and is how a deferred change lands.
Driving this from a script? Use a key
Cache exclusions on the CDN
One path prefix per line, starting and ending with a slash. Each line becomes its own CDN record.
Check real edge behaviour
Requests the path three times through the CDN. The test origin returns a new value every time, so a repeated value proves a cache hit.
Purge
Clears cached objects under a path prefix on the test site.
Edge rules from the plugin
What the current gateway really offers: country blocking, hotlink protection and an allowed-method list. Written to every record of this site, the exclusions included, because a record holds no per-path rules. Empty removes a rule.
Traffic, last 24 hours
The CDN reports per account, never per site, so these counters cover the whole development account. A per-site number in the plugin needs a change on the vendor side.
What the current gateway can and cannot do
| Capability | Status | How |
|---|
Engineering evidence & what unlocks a live demo
A documented route, with one critical check
The published API documents a gateway and runtime discovery of rewrite options in a customer shortname and DeliveryTemplate context. The schema for the exact exclusion option still needs authenticated discovery.
- Discover options. Request the approved template with the customer shortname.
GET /apigw/v1/config/option/deliveryTemplate/{deliveryTemplateName}?shortname={shortname}&size=all - Read the existing delivery. Preserve a complete baseline. The documented delivery
PUTis a full replacement, so submitting only one changed field is unsafe. - Map and validate the exclusion option. The vendor’s actual regex dialect, escaping, limits and precedence are unverified. This prototype deliberately uses a small local path grammar.
- Write, then read back. Check the saved record, job completion where applicable, edge propagation and actual HTTP cache behavior on an approved test site. API readback alone does not prove edge behavior.
Ask EdgePrizm for this development package
- A least-privilege development
client_idandclient_secret, scoped to a test customer. Store credentials on the server, never in the browser or this artifact. - The customer
shortname, delivery UUID, exact DeliveryTemplate and permitted read/write scope. - An approved disposable WordPress test site, origin and onboarding instructions for DNS ownership, TLS and rollback.
- A working exclusion-option example, allowed syntax, limits, activation timing and a successful update/readback example.
- Confirmation of the image transformation endpoint and entitlement, if it belongs in the first release.
What this demo proves: the small UI can be built and its interaction tested now. It does not prove authenticated API access, complete onboarding or safe cache behavior.