An issue exists in the `nginx.conf` file where the use of the backend-facing `$scheme` variable in the trailing-slash directory redirect allows an on-path network attacker to read or modify documentation content. This occurs when a victim makes an HTTPS request for a slashless directory path; since TLS terminates at the load balancer in front of Nginx, the resulting 301 response redirects the client to a plaintext http:// URL. This affects clients that do not enforce HSTS (HTTP Strict Transport Security), such as scripts that follow redirects and command-line HTTP clients. Browsers with a preloaded HSTS list are not affected due to the .dev top-level domain being preloaded.