From 76daa5bf331a94a52957866e723b469c29f4c75e Mon Sep 17 00:00:00 2001
From: Tim Perry <pimterry@gmail.com>
Date: Tue, 5 Dec 2017 20:06:53 +0100
Subject: [PATCH] Fix proxy url

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 41fc255..75c0079 100644
--- a/README.md
+++ b/README.md
@@ -24,7 +24,7 @@ curl -k --proxy-insecure -x https://localhost:8000 https://example.com
 You can start a fresh Chrome session using this proxy & trusting the cert with:
 
 ```
-google-chrome --user-data-dir=/tmp/chrome --proxy-server="https://localhost:80" --ignore-certificate-errors-spki-list=AvVrqB/anBbJ+KRCMH/anWgZbeE0Y28JtqYB0+2MDmE=
+google-chrome --user-data-dir=/tmp/chrome --proxy-server="https://localhost:8000" --ignore-certificate-errors-spki-list=AvVrqB/anBbJ+KRCMH/anWgZbeE0Y28JtqYB0+2MDmE=
 ```
 
 After a minute of heavy use the proxy will crash with SIGSEGV/SIGABRT, I think always in CRYPTO_free, and typically inside DestroySSL.