Routes are used to determine which applications are used to handle a request to your project.
Filters are applied during routing to further determine which routes are used to handle a request. Filter values can be any valid RegEx. A route filter must define a path filter, and additionally the other filter types to route the request at an application.
Path filters allow you to target the incoming path of a request, and are used with all types of processors. A path filter is required for every route filter definition.
Query String Filters
Query string filters allow you to target specific query string attributes, and are often best used with APIs, redirects and OAuth processors. When using query filters with view package processors, make sure to keep in mind that the query string will not be added to child requests (scripts, css, images).
Header filters work great with all the different types of processors, but do require a bit of extra configuration. You'll need to add some sort of extension to your browser (like ModHeader for Chrome) to use these while browsing your site. This works great for view packages, as all child requests (except for limited types like web socket connections) do receive the header, allowing for dynamic testing scenarios.