Automating Service Discovery with Traefik Docker Labels
Stop manually updating proxy configs. Learn how to use Traefik's Docker provider to automate service discovery and routing using container labels.
Loading…
ReadMeFeed / Community knowledge
#reverse-proxy
Real questions. Useful conversations. Find the people who know your stack.
Distributing Traffic with NGINX Upstream Load Balancing
Learn how to implement NGINX upstream load balancing to distribute traffic across multiple servers using Round Robin, weighted distribution, and session persistence.
nginxConfiguring Varnish Cache for Magento 2 to Reduce TTFB
Learn how to implement Varnish Cache for Magento 2 to drastically reduce TTFB and server load by offloading HTML delivery to a high-performance reverse proxy.
magentoApache HTTP Server as a Simple Reverse‑Proxy Load Balancer with mod_proxy_balancer
Learn the minimal Apache 2.4 setup needed to load‑balance HTTP traffic using mod_proxy_balancer, including configuration, trust boundaries, and operational checks.
Architecture Note: Using NGINX limit_req for Edge‑Side Rate Limiting
A concise guide to designing a minimal NGINX reverse‑proxy setup that enforces request‑rate limits with the limit_req module, covering requirements, trust boundaries, operational checks, failure modes, and when the design must evolve.
Resolving Mattermost WebSocket Failures and 502 Bad Gateway in Reverse Proxies
A guide to fixing Mattermost WebSocket failures and 502 errors caused by misconfigured reverse proxies and timeout settings.
Blazor Server Circuit Persistence With Proxy-Handled WebSocket Upgrades
Goal: reconcile Blazor Server circuit lifecycle events with reverse proxy WebSocket timeout behavior to maintain persistent connections without unnecessary disconnections. Constraint/uncertainty: SignalR's KeepAliveInterval and AutoDisconnectTimeout are calculated on the client-side circuit handler, but when an intermediate proxy or load balancer terminates
blazorLimits of proxy_ignore_client_abort: can nginx finish upstream work after the client disconnects?
I'm designing an nginx reverse proxy in front of a slow upstream that performs long, idempotent processing (report generation). Clients frequently disconnect before the response arrives, and I want the upstream work to still complete so results are logged and cached server-side, even though the response itself can never be delivered. My reading of the ngx_ht
Redirect loop behind a TLS-terminating proxy when SECURE_PROXY_SSL_HEADER is unset
A Django deployment served behind a reverse proxy that terminates TLS is documented to look like plain HTTP to the application unless SECURE_PROXY_SSL_HEADER is configured. When SECURE_SSL_REDIRECT is enabled at the same time, Django keeps redirecting an already-HTTPS request back to HTTPS, producing a redirect loop. Locally, without a proxy, the same settin
django