Test Configuration Options
Before applying a configuration change to your entire site, you can test it on individual requests using a Conditional Rule gated by a query parameter. Only your request gets the new behavior — every other visitor keeps the current configuration.
How It Works
- Create a Conditional Rule that matches a specific URL parameter.
- In the rule's settings, override the configuration you want to test.
- Open your site with the test parameter appended to the URL.
- Compare the result with the same URL without the parameter.
Examples
Test image quality
Try a different JPEG quality setting before applying it site-wide:
| Field | Value |
|---|---|
| Condition | Query parameter test-jpeg equals 1 |
| Override | JPEG quality target: 0.9990 (lower than your default) |
https://example.com/products/image.jpg?test-jpeg=1Test WebP disabled
Check how a page behaves without WebP conversion:
| Field | Value |
|---|---|
| Condition | Query parameter no-webp equals 1 |
| Override | WebP conversion: disabled |
https://example.com/products/image.jpg?no-webp=1Test cache bypass
Skip the cache for one specific request to see the raw origin response:
| Field | Value |
|---|---|
| Condition | Query parameter nocache equals 1 |
| Configuration | Site Configuration: off |
https://example.com/category/page.html?nocache=1Tips
- Use unique parameter names that won't collide with parameters your application already uses.
- Combine with Debug Headers — enable Debug Headers in your site's Basic Configuration to see exactly how the test rule affects caching, image optimization, and routing on each request.
- Remove test rules once the change is rolled out into the main configuration. Leftover test rules add unnecessary processing on every request.
- Share the test URL with teammates so they can review the change before it goes live.
Related
- Conditional Rules — full reference for condition matching and configuration overrides
- Cache Invalidation — clear cached content after rolling out a change