From 2a857084b40b6c84b891278858b31d5d06321284 Mon Sep 17 00:00:00 2001
From: steveninouye <31404557+steveninouye@users.noreply.github.com>
Date: Tue, 6 Mar 2018 16:21:13 -1000
Subject: [PATCH] Added detail to ###Testing

I spent over 5 hours trying to get the response body.  On line 116 it says to display the response body so I used www.devleague.com to test my code with public hosts.  Of course that did not work so I feel that needs to be clear to the developer.
---
 README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 310b77d..0f65bc5 100644
--- a/README.md
+++ b/README.md
@@ -137,13 +137,17 @@ Parse the response headers, and store them in a hash table for later use.
 
 ### Testing
 
-Test by requesting web servers with domain names, and your own running `server.js`
+Test by requesting web servers with domain names, and your own running `server.js`. You should be able to acquire headers
+
+
 
 ```
 node client.js www.devleague.com
 node client.js localhost
 ```
 
+*Note*: You will not be able to acquire the response body of sites using the https protocol as you will be trying to connect over a secured port without a proper SSL handshake
+
 ### Features
 
 1. Pipe the response content stream to stdout