#apachetrafficserver — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #apachetrafficserver, aggregated by home.social.
-
CVE-2025-49763: Apache Traffic Server Vulnerability Enables Memory Exhaustion Attacks https://thecyberexpress.com/apache-traffic-server-cve-2025-49763/ #ApacheTrafficServer #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CVE202549763 #CyberNews #ACLissue #ATS
-
CVE-2025-49763: Apache Traffic Server Vulnerability Enables Memory Exhaustion Attacks https://thecyberexpress.com/apache-traffic-server-cve-2025-49763/ #ApacheTrafficServer #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CVE202549763 #CyberNews #ACLissue #ATS
-
I spent WEEKS trying to get #Squid #ProxyServer to act as a forward-proxy for our instances and cache both HTTP & HTTPS traffic with absolutely no luck.
Installed #ApacheTrafficServer this evening and had everything up and running in 30 minutes.
Jesus fucking Christ.
This shouldn't have been that difficult. -
Fastly uses the H2O reverse proxy for fast and secure TLS termination over QUIC, HTTP/3, HTTP/2, and 1.1.
The project site compares its benchmarks only to Nginx. I'd love to see a more recent comparison that includes ATS (Apache Traffic Server), HAProxy, and Varnish/Hitch as fellow reverse proxies for TLS termination.
https://www.fastly.com/blog/tls-more-secure-always-fast
via @devs and https://ieji.de/@SolSoCoG/109392993726218659
#webperf #nginx #varnish #apachetrafficserver #H2O #fastly #HAProxy
-
Fastly uses the H2O reverse proxy for fast and secure TLS termination over QUIC, HTTP/3, HTTP/2, and 1.1.
The project site compares its benchmarks only to Nginx. I'd love to see a more recent comparison that includes ATS (Apache Traffic Server), HAProxy, and Varnish/Hitch as fellow reverse proxies for TLS termination.
https://www.fastly.com/blog/tls-more-secure-always-fast
via @devs and https://ieji.de/@SolSoCoG/109392993726218659
#webperf #nginx #varnish #apachetrafficserver #H2O #fastly #HAProxy
-
@samuel if your content is (partly, semi) static, using a caching reverse proxy can help reduce bandwidth used on your origin uplink and improve "speed" (reduce latencies, increase bandwidth) for your users. some options are #apachetrafficserver #freenginx and #varnishcache, only to name a few. my recommendation should be obvious, but you have the choice and a lot of options.
as a pure (non caching) forwarding tcp or http proxy #haproxy is a good choice.