> For the complete documentation index, see [llms.txt](https://mazeframework.gitbook.io/maze/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mazeframework.gitbook.io/maze/guides/routing.md).

# Routing

The Maze router recognizes URLs and dispatches them to a controller's action. It can also generate paths and URLs, avoiding the need to hardcode strings in your views.

## Pipelines

A *pipeline* is a set of of transformations that is performed to a HTTP request. These transformations come in the form of a pipe. A *pipe* is a \_\*\*\_class which includes [`HTTP::Handler`](https://crystal-lang.org/api/latest/HTTP/Handler.html) and implements the [`#call`](https://crystal-lang.org/api/latest/HTTP/Handler.html#call\(context%3AHTTP%3A%3AServer%3A%3AContext\)-instance-method) method. You can use a handler to intercept any incoming request and modify the response. These can be used for request throttling, ip-based whitelisting, adding custom headers.

{% content-ref url="/pages/-LDM0m7eKHx7sU-GAOnK" %}
[Pipelines](/maze/guides/routing/pipelines.md)
{% endcontent-ref %}

## Routes

Routing provides you tools that map URLs to controller actions. By defining routes, you can separate how your application is implemented from how its URL’s are structured, Routes wire up real-time web socket handlers, and define a series of pipeline transformations for scoping middleware to sets of routes.

{% content-ref url="/pages/-LDM0m7fOENI3TP30Z9v" %}
[Routes](/maze/guides/routing/routes.md)
{% endcontent-ref %}