เครื่องหมายทับท้ายและพฤติกรรมการเปลี่ยนเส้นทาง

To Flask, /about and /about/ can be two different things. That tiny trailing slash decides how a route matches and whether a redirect happens.

When your route ends in a slash, it behaves like a folder. Visiting /docs/ works, and /docs gets redirected to the slashed version. 📁

A route with no trailing slash behaves like a file. Here /docs works, but /docs/ returns a 404 instead of redirecting.

For folder-style routes, Flask helpfully redirects the slashless URL to the canonical one. This keeps a single canonical address for that page.

The kindness only flows one direction. A file-style route will not redirect from /docs/ to /docs; the extra slash simply yields a 404.

One canonical URL per page avoids duplicate addresses. That helps caching, analytics, and SEO, since search engines see a single canonical link.

Let url_for generate links and you always get the canonical slash form. You never have to remember which routes end in a slash.

Choose one style across your app, often no trailing slash for endpoints. A steady convention means fewer surprise 404s for your users.

A redirect sends a 301 or 308 back, and the browser then requests the new URL. That is one extra round trip you avoid by linking correctly.

Slash redirects on a POST can drop the body or change the method. Always post to the exact canonical URL to keep your data intact.

When debugging a missing page, try the URL with and without the slash. The difference often reveals a mismatch between your link and your route.

Your route is @app.route('/docs') with no trailing slash. What does visiting /docs/ return?

A trailing slash makes a route folder-like and redirects to its canonical form; without one it is strict. Lean on url_for and stay consistent. 🎉