From 98fced4cd9bbe04b40e9a95234058df3dc63a239 Mon Sep 17 00:00:00 2001
From: Noah Levitt <nlevitt@archive.org>
Date: Wed, 16 Oct 2013 14:50:08 -0700
Subject: [PATCH] explain about CA trust in readme

---
 README.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index cc7d0ac..32cf8db 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,15 @@
-#warcprox - WARC writing MITM HTTP/S proxy
+##warcprox - WARC writing MITM HTTP/S proxy
 
 Based on the excellent and simple pymiproxy by Nadeem Douba.
 https://github.com/allfro/pymiproxy
 
 License: because pymiproxy is GPL and warcprox is a derivative work of
 pymiproxy, warcprox is also GPL.
+
+###Trusting the CA cert
+
+For best results while browsing through warcprox, you need to add the CA cert
+as a trusted cert in your browser. If you don't do that, you will get the
+warning when you visit each new site. But worse, any embedded https content on
+a different server will simply fail to load, because the browser will reject
+the certificate without telling you.