Trailing slash behavior in FastAPI - Step-by-Step Execution

Concept Flow - Trailing slash behavior

Client sends request URL

↓

Check if URL ends with slash

↓

Match route with slash

↓

Return response

FastAPI checks if the request URL ends with a slash and matches it to the route with or without a trailing slash, possibly redirecting if needed.

Execution Sample

FastAPI

from fastapi import FastAPI
app = FastAPI()

@app.get("/items/")
async def read_items():
    return {"msg": "Trailing slash route"}

Defines a route with a trailing slash and returns a message when accessed.

Execution Table

Step	Request URL	Trailing Slash?	Route Matched	Response or Redirect
1	"/items/"	Yes	"/items/" route	Returns {"msg": "Trailing slash route"}
2	"/items"	No	No exact match	Redirects to "/items/" (status 307)
3	"/items/"	Yes	After redirect, matches "/items/"	Returns {"msg": "Trailing slash route"}
4	"/unknown"	No	No match	Returns 404 Not Found

💡 Execution stops after response or 404 error is returned.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
Request URL	None	"/items/"	"/items"	"/items/" (after redirect)	"/unknown"
Trailing Slash?	None	True	False	True	False
Route Matched	None	"/items/"	None	"/items/"	None
Response	None	200 OK with message	307 Redirect	200 OK with message	404 Not Found

Key Moments - 3 Insights

Why does accessing "/items" redirect to "/items/"?

Because the route is defined with a trailing slash, FastAPI redirects requests without the slash to the correct route to keep URLs consistent, as shown in step 2 and 3 of the execution_table.

What happens if the route is defined without a trailing slash and the request has one?

FastAPI will redirect the request with the trailing slash to the route without it, similar to the opposite case, ensuring consistent URL matching.

Why does accessing an unknown URL return 404?

Because no route matches the requested URL, FastAPI returns a 404 Not Found error as shown in step 4 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what response does FastAPI give when requesting "/items" initially?

A Returns 200 OK with message

B Redirects to "/items/" with status 307

C Returns 404 Not Found

D Returns 500 Internal Server Error

💡 Hint

Check step 2 in the execution_table where the request URL is "/items" without trailing slash.

At which step does the request URL change due to redirect?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the Request URL variable in variable_tracker after step 3.

If the route was defined without a trailing slash, what would happen when requesting "/items/"?

A Return 404 Not Found

B Return 200 OK immediately

C Redirect to "/items" without slash

D Cause server error

💡 Hint

Based on key_moments about opposite redirect behavior for trailing slash.

Concept Snapshot

FastAPI routes can end with or without a trailing slash.
Requests must match the route's slash pattern.
If not matched, FastAPI redirects to the correct URL.
This keeps URLs consistent and avoids duplicate content.
Trailing slash behavior affects route matching and redirects.

Full Transcript

This visual execution shows how FastAPI handles trailing slashes in URLs. When a client requests a URL, FastAPI checks if it ends with a slash and tries to match it to a route defined with or without a trailing slash. If the request URL does not exactly match the route, FastAPI issues a redirect to the correct URL with or without the trailing slash. For example, a route defined as "/items/" will redirect requests to "/items" to "/items/". If no route matches, FastAPI returns a 404 error. This behavior ensures consistent URLs and helps avoid confusion or duplicate content. The execution table traces requests with and without trailing slashes, showing when redirects happen and what responses are returned.