Skip to content

Test Configuration Options

Before applying a configuration change to your entire zone, 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

  1. Create a Conditional Rule that matches a specific URL parameter.
  2. In the rule's settings, override the configuration you want to test.
  3. Open your zone with the test parameter appended to the URL.
  4. Compare the result with the same URL without the parameter.

Examples

Test image quality

Try a different JPEG quality setting before applying it zone-wide:

FieldValue
ConditionQuery parameter test-jpeg equals 1
OverrideJPEG quality target: 0.9990 (lower than your default)
https://example.com/products/image.jpg?test-jpeg=1

The JPEG quality target is an SSIM target on a 0.00010.9999 scale, where higher values stay closer to the original. The default is 0.9997, so 0.9990 is a lower target that compresses slightly more aggressively.

Test WebP disabled

Check how a page behaves without WebP conversion:

FieldValue
ConditionQuery parameter no-webp equals 1
OverrideWebP conversion: disabled
https://example.com/products/image.jpg?no-webp=1

Test cache bypass

Skip the cache for one specific request to see the raw origin response:

FieldValue
ConditionQuery parameter nocache equals 1
ConfigurationZone Configuration: off
https://example.com/category/page.html?nocache=1

Tips

  • Use unique parameter names that won't collide with parameters your application already uses.
  • Combine with Debug Headers - enable Debug Headers in your zone's Proxy 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.