Traefik Reviews

TinyProxy Reviews

1. Stan

   · Founder at SaaSHub · over 6 years ago
   It was easier to install and use than expected

   Super simple and straight to the point. All I had to do, in a linux server, was this:

   • install it => apt install tinyproxy
   • configure hosts allowed to connect
   • reload configs => service tinyproxy reload

   🏁 Competitors: banu.com TinyProxy, Squid Proxy

   👍 Pros:    Super simple|Easy to use

Traefik mentions (43)

• My homelab stack in 2026: what runs, why, and how it all connects

  Everything HTTP goes through Traefik. It's the reverse proxy in front of every Docker-hosted service, and the main reason I chose it over Nginx or Caddy is Docker-native autodiscovery. When I bring up a new container with the right labels, it appears behind a subdomain with automatic TLS, no config file reload required. That removes enough friction that I'm less tempted to leave things running unproxied on bare... - Source: dev.to / 30 days ago

• Traefik vs HAProxy: Reverse Proxy Showdown

  Traefik (v3.6) is a cloud-native edge router that watches Docker, Kubernetes, and other providers for service changes. When you deploy a new container with the right labels, Traefik automatically creates a route and provisions an SSL certificate. Configuration is split between a static config file (entry points, providers) and dynamic config (Docker labels on each service). - Source: dev.to / 4 months ago

• Traefik vs Caddy: Which Reverse Proxy?

  Traefik (v3.6) is a cloud-native edge router written in Go. It watches Docker, Kubernetes, and other providers for service changes and automatically creates routes based on labels. Configuration is split between a static config file and dynamic config via labels or files. Traefik has been around since 2016 and is widely used in production orchestration environments. - Source: dev.to / 4 months ago

• Controlling Kubernetes Network Traffic – Part 1

  Traefik is a modern, cloud-native reverse proxy and load balancer that also serves as a Kubernetes Ingress Controller. It acts as an in-cluster application that integrates with the Kubernetes API to automatically detect Ingress resources and dynamically configure itself to route incoming HTTP/HTTPS traffic to the appropriate backend services within the cluster. - Source: dev.to / 8 months ago

• Why We Moved API Authentication from the Gateway to Our Microservices

  Then we started looking into Kong alternatives, and found multiple options: Envoy, Traefik, etc... But migrating from Kong plugin into those would be a bit painful and wasn't guaranteed to be smooth as we use a single domain and it can point to only one of those Ingress controllers. - Source: dev.to / 9 months ago

TinyProxy mentions (8)

• Duct tape enough services together and you can cache APT packages

  The first result led me to TinyProxywhich was the exactly what I needed. It’s a small, proxy server that handles forwarding HTTPS requests, requiring almost zero configuration, and has on-going maintenance. Adding it to the container and updating HAProxy to pass the appropriate traffic to it filled in the missing piece. It would handle HTTPS traffic while Nginx continued to handle caching. - Source: dev.to / 4 months ago

• Overcoming Geo-Blocked Feature Testing with Zero-Budget DevOps Strategies

  Leverage open-source proxy tools like mitmproxy or tinyproxy, which allow you to intercept and modify HTTP requests and responses in real-time. By configuring these, you can simulate different geo conditions:. - Source: dev.to / 6 months ago

• I Add 3-25 Seconds of Latency to Every Page I Visit (2020)

  Probably by modifying the source code of https://tinyproxy.github.io (it's a lightweight proxy, but modifying the source would be not a 5-minute thing...). - Source: Hacker News / about 2 years ago

• Web Debugging Proxy to Remove Headers from Incoming Requests

  I found Privoxy, and it seems to do what I want, so maybe wondering if anyone would be eager to recommend. There is also Tinyproxy, but it can only add headers not remove them. Source: over 2 years ago

• Chromium Spelunking: Connecting to Proxies

  To test proxying,I'm using tinyproxy, running a very simple config on port 8080. This supports SPDY (HTTP/2), which is a complication I don't really want to consider at this point, but the analysis ends up quite similar to HTTP/1. - Source: dev.to / almost 3 years ago