Why a Missing Slash in Nginx proxy_pass Breaks Your Site – Deep Dive

Background

Nginx is a lightweight, high‑performance web server widely adopted by large Chinese internet companies. Because its behavior is driven by configuration files, a tiny mistake—such as omitting a single "/" character—can cause request failures and customer complaints.

Location Matching Basics

Each location block defines a URL prefix that Nginx matches from top to bottom. When a request matches a location, the directives inside its braces are applied.

Example Configuration

location /wddd/ {
    proxy_connect_timeout 18000;   # 5 hours
    proxy_send_timeout    18000;
    proxy_read_timeout    18000;
    proxy_pass            http://127.0.0.1:8080;
}

With this configuration, a request to http://www.wandouduoduo.com/wddd/index.html is proxied to the local Tomcat service on port 8080, and the response is returned unchanged.

Effect of the Trailing Slash in location

If the location pattern ends with "/", it matches only the exact directory. Without the trailing slash, the pattern performs a fuzzy match on any URI that starts with the given string.

Four proxy_pass Variants

Trailing slash in proxy_pass

location /wddd/ {
    proxy_pass http://127.0.0.1:8080/;
}

Result: request is forwarded to http://127.0.0.1:8080/index.html.

No trailing slash in proxy_pass

location /wddd/ {
    proxy_pass http://127.0.0.1:8080;
}

Result: request is forwarded to http://127.0.0.1:8080/wddd/index.html.

Trailing slash with additional path

location /wddd/ {
    proxy_pass http://127.0.0.1:8080/sun/;
}

Result: request is forwarded to http://127.0.0.1:8080/sun/index.html.

Additional path without trailing slash

location /wddd/ {
    proxy_pass http://127.0.0.1:8080/sun;
}

Result: request is forwarded to http://127.0.0.1:8080/sunindex.html.

Summary of Findings

Adding "/" after a location makes the match exact; omitting it allows fuzzy matching of any URI that starts with the prefix.

Whether proxy_pass ends with a slash or not determines how the upstream URL is constructed: the upstream path is concatenated directly to the request URI when the slash is missing.

Full Test Configuration

server {
    listen 80;
    server_name localhost;

    # /wddd01/xxx  -> http://localhost:8080/wddd01/xxx
    location /wddd01/ {
        proxy_pass http://localhost:8080;
    }

    # /wddd02/xxx  -> http://localhost:8080/xxx
    location /wddd02/ {
        proxy_pass http://localhost:8080/;
    }

    # /wddd03xxx  -> http://localhost:8080/wddd03xxx
    location /wddd03 {
        proxy_pass http://localhost:8080;
    }

    # /wddd04/xxx  -> http://localhost:8080//xxx (double slash)
    location /wddd04 {
        proxy_pass http://localhost:8080/;
    }

    # /wddd05/xxx  -> http://localhost:8080/hahaxxx (missing slash between prefix and path)
    location /wddd05/ {
        proxy_pass http://localhost:8080/haha;
    }

    # /wddd06/xxx  -> http://localhost:8080/haha/xxx
    location /wddd06/ {
        proxy_pass http://localhost:8080/haha/;
    }

    # /wddd07/xxx  -> http://localhost:8080/haha/xxx (no trailing slash in location)
    location /wddd07 {
        proxy_pass http://localhost:8080/haha;
    }

    # /wddd08/xxx  -> http://localhost:8080/haha//xxx (double slash in upstream)
    location /wddd08 {
        proxy_pass http://localhost:8080/haha/;
    }
}

Running these configurations lets readers observe how subtle differences in slashes affect the final proxied URL, reinforcing the importance of precise Nginx syntax.