diff --git a/README.md b/README.md
index f6516249eb..70b56fb6cc 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@ NaïveProxy uses Chromium's network stack to camouflage traffic with strong cens
 
 The following traffic attacks are mitigated by using Chromium's network stack:
 
-* Website fingerprinting / traffic classification: [mitigated](https://arxiv.org/abs/1707.00641) by traffic multiplexing in HTTP/2.
+* Website fingerprinting / traffic classification: mitigated by [traffic multiplexing in HTTP/2](https://arxiv.org/abs/1707.00641) and parroting preambles.
 * [TLS parameter fingerprinting](https://arxiv.org/abs/1607.01639): defeated by reusing [Chrome's network stack](https://www.chromium.org/developers/design-documents/network-stack).
 * [Active probing](https://ensa.fi/active-probing/): defeated by *application fronting*, i.e. hiding proxy servers behind a commonly used frontend server with application-layer routing.
 * Length-based traffic analysis: mitigated by length padding.
@@ -41,9 +41,13 @@ Example Caddyfile (replace `user` and `pass` accordingly):
 ```
 {
   order forward_proxy before file_server
+  log {
+    exclude http.log.error # Avoid logging user activity
+  }
 }
 :443, example.com {
   tls me@example.com
+  encode
   forward_proxy {
     basic_auth user pass
     hide_ip