Rust & Rocket Tutorial, the URL path

In the previous tutorial we created a working development environment and compiled the Rocket.Rs getting started example.

In this article we will talk about HTTP requests and how they are handled by Rocket.Rs.

The function we wrote in the previous article is called a route, and it’s registered in the main function. As you can see, the request path is used to route the request to the correct handler:

fn index() -> &'static str {
    "Hello, world!"

rocket::ignite().mount("/", routes![index]).launch();

Just to conferm our understanding, let’s try creating another route and testing it:

fn say_hello() -> String {

rocket::ignite().mount("/", routes![index, say_hello]).launch();

When we run our program using cargo run, as we did in the previous article, we obtain the following result:

$ cargo run
🛰  Mounting '/':
    => GET /
    => GET /hello
🚀  Rocket has launched from http://localhost:8000

$ curl http://localhost:8000/hello/

It works! But we can also receive parameters from url segments, like in the following example:

fn say_hello(name: String) -> String {
    format!("Hello, {}!", name)
$ curl http://localhost:8000/hello/leonardo/
Hello, leonardo!

It works! Let’s try what happens adding another parameter, the age:

fn say_hello(name: String, age: i32) -> String {
    format!("Hello, {}! Your age is {}.", name, age)
$ curl http://localhost:8000/hello/leonardo/37
Hello, leonardo! Your age is 37.

Let’s try what happens if we use a wrong age…

$ curl http://localhost:8000/hello/leonardo/thirtysevel
<!DOCTYPE html>
    <meta charset="utf-8">
    <title>404 Not Found</title>
<body align="center">
    <div align="center">
        <h1>404: Not Found</h1>
        <p>The requested resource could not be found.</p>
        <hr />

The URLs are type safe, and a wrong age can’t be passed to this route, simply because it can’t be applied.

We can also write a catch-all route and use that to serve files from the file system:

fn files(file: PathBuf) -> Option<NamedFile> {

With the previous rule, a request like http://localhost:8000/static/test.css will be served loading a file named static/test.css. We will use this strategy to serve the static assect of the web application we will build in our tutorial.

In the next post we will introduce the template engine.