> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/the-basics/routing/routing-dsl/routing-conditions.md).

# Routing Conditions

withCondition() attaches a runtime closure check so a matched route only fires when the condition returns true.

`withCondition()` attaches a runtime check to a route. Even if the URL pattern matches, the route only fires if the closure returns `true`.

```javascript
route( "/go/firefox" )
    .withCondition( ( requestString ) => {
        return findNoCase( "Firefox", cgi.HTTP_USER_AGENT ) ? true : false;
    } )
    .to( "firefox.index" );
```

This is useful for things like browser sniffing, feature flags, or A/B routing - any case where the URL alone isn't enough to decide whether a route should apply.

{% hint style="info" %}
A condition only decides **whether** the route matches. It doesn't stop or shape the request the way [route middleware](/the-basics/routing/routing-dsl/middleware.md) does - if you need to reject, redirect, or transform the request once matched, middleware is the right tool.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox.ortusbooks.com/the-basics/routing/routing-dsl/routing-conditions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.