Opened 8 weeks ago

#2608 new enhancement

Request to Add Documentation Link on Trailing Slash Behavior in Reverse Proxy Setup

Reported by: leerenix@… Owned by:
Priority: trivial Milestone:
Component: documentation Version: 1.18.x
Keywords: reverse proxy, docs Cc:
uname -a:
nginx -V: nginx version: nginx/1.18.0 (Ubuntu)
built with OpenSSL 3.0.2 15 Mar 2022
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -ffile-prefix-map=/build/nginx-zctdR4/nginx-1.18.0=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,-z,now -fPIC' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/ --modules-path=/usr/lib/nginx/modules --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-compat --with-debug --with-pcre-jit --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_v2_module --with-http_dav_module --with-http_slice_module --with-threads --add-dynamic-module=/build/nginx-zctdR4/nginx-1.18.0/debian/modules/http-geoip2 --with-http_addition_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_sub_module


Hello! I've noticed an inconsistency that seems counterintuitive related to the behavior of proxy formatting based on the presence or absence of a trailing slash in the proxy_pass directive. Although this detail is documented, it is not immediately apparent or accessible on the initial pages that one might consult when setting up a reverse proxy.

Furthermore, the documentation page (,in%20some%20cases) that discusses this behavior, despite being relevant to reverse proxies, does not have any direct links from the main reverse proxy documentation page ( I encountered a problem related to a trailing slash that took me two days to resolve, and my solution came from a blog post that referenced the detailed documentation. While I understand there may not be changes to the logic governing this behavior, could a direct link to the detailed page be added to the main reverse proxy documentation? This could significantly aid others in troubleshooting and understanding configuration nuances.

Change History (0)

Note: See TracTickets for help on using tickets.