@@ -75,6 +75,7 @@ Memory, disk exhaustion? Performance issues?
# Reference
## Installation
<!-- how to setup the service from scratch -->
Include `roles::cache` in Puppet.
...
...
@@ -103,7 +104,7 @@ the [proxy module](https://nginx.org/en/docs/http/ngx_http_proxy_module.html) fo
DNS for the site points to `cache.torproject.org`, an alias for the
caching servers, which are currently two: `cache01.torproject.org`
[[sic](https://en.wikipedia.org/wiki/Sic)] and `cache-02`. An HTTPS certificate for the site was
\[[sic](https://en.wikipedia.org/wiki/Sic)\] and `cache-02`. An HTTPS certificate for the site was
issued through [howto/letsencrypt](howto/letsencrypt). Like the Nginx configuration, the
certificate is deployed by Puppet in the `roles::cache` class.
...
...
@@ -576,7 +577,7 @@ Other alternatives were not:
*[Envoy][] - [not designed for caching](https://github.com/envoyproxy/envoy/issues/868), [external cache support
planned in 2019](https://blog.getambassador.io/envoy-proxy-in-2019-security-caching-wasm-http-3-and-more-e5ba82da0197?gi=82c1a78157b8)
*[HAproxy](https://www.haproxy.com/) - [not designed to cache large objects](https://www.haproxy.com/documentation/aloha/9-5/traffic-management/lb-layer7/caching-small-objects/)
*[H2O](https://h2o.examp1e.net/) - HTTP/[123], written from scratch for HTTP/2+, presumably
*[H2O](https://h2o.examp1e.net/) - HTTP/\[123\], written from scratch for HTTP/2+, presumably
faster than Nginx, didn't find out about it until after the project
launched
*[Ledge](https://github.com/ledgetech/ledge) - caching extension to Nginx with ESI, Redis, and cache
...
...
@@ -632,7 +633,6 @@ Cons:
* couldn't figure out how to make HTTP/2 work
* no prometheus exporters
#### Configuration
apt install trafficserver
...
...
@@ -689,7 +689,7 @@ And finally curl is able to talk to the proxy:
#### Troubleshooting
##### Proxy fails to hit backend:
##### Proxy fails to hit backend
curl: (56) Received HTTP code 404 from proxy after CONNECT
