Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
The characters ?, +, "8", and () are subsets of their regular expression counterparts. The hyphen (-) and the dot (.) are interpreted literally by string-based paths.
Here are some examples of route paths based on strings.
```go
// This route path will match requests to the root route, /.
app.Get("/", func(c *fiber.Ctx) {
c.Send("root")
})
// This route path will match requests to /about.
app.Get("/about", func(c *fiber.Ctx) {
c.Send("about")
})
// This route path will match requests to /random.text.
Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values can be retrieved using the [Params](context#params) function, with the name of the route parameter specified in the path as their respective keys.
To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
The [Next](context#next) function is a function in the [Fiber](https://github.com/fenny/fiber) router which, when called, executes the next function that matches the current route.
Functions that are designed to make changes to the request or response are called middleware functions.
// Use method path is a "mount" or "prefix" path and limits the middleware to only apply to any paths requested that begin with it. This means you cannot use :params on the Use method