# Test configuration options

Before applying configuration changes to your entire site, you can test them on individual requests using [Conditional Rules](https://docs.smoxy.eu/en/rules/conditional-rules) with URL parameters. This lets you verify that a change works as expected without affecting any other visitors.

***

### 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 site with the test parameter in the URL
4. Only your request uses the new settings — everyone else gets the current configuration

***

### Examples

#### Test Image Quality

Test a lower 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 default `0.9997`) |

```
https://example.com/products/image.jpg?test-jpeg=1
```

Compare the result with the same URL without the parameter to see the quality difference.

#### Test WebP Disabled

Check how your site performs without WebP conversion:

| Field         | Value                                |
| ------------- | ------------------------------------ |
| **Condition** | Query parameter `no-webp` equals `1` |
| **Override**  | WebP conversion: disabled            |

```
https://example.com/products/image.jpg?no-webp=1
```

#### Test Cache Bypass

Temporarily skip the cache for a specific request to see the origin response:

| Field                  | Value                                |
| ---------------------- | ------------------------------------ |
| **Condition**          | Query parameter `nocache` equals `1` |
| **Site-Configuration** | `off`                                |

```
https://example.com/category/page.html?nocache=1
```

***

### Tips

* **Use unique parameter names** that won't conflict with your application's actual query parameters
* **Combine with Debug Headers** — enable Debug Headers to see exactly how your test rule affects caching, image optimization, and routing
* **Remove test rules** after you've verified your changes and applied them to the site configuration — leaving unused rules adds unnecessary processing
* **Share test URLs** with your team to get feedback on configuration changes before going live