From 8b52f445022c1136d2361a00c3583b3a49b3a1c7 Mon Sep 17 00:00:00 2001
From: Alex Reisner <alex@alexreisner.com>
Date: Sun, 5 Oct 2014 15:18:04 -0400
Subject: [PATCH] Add code to fetch raw server response.

---
 README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 879176e0..cf6b03d0 100644
--- a/README.md
+++ b/README.md
@@ -980,12 +980,16 @@ A lot of debugging time can be saved by understanding how Geocoder works with Ac
 
 ### Unexpected Responses from Geocoding Services
 
-Take a look at the server's raw JSON response. You can do this by getting the request URL in an app console:
+Take a look at the server's raw response. You can do this by getting the request URL in an app console:
 
     Geocoder::Lookup.get(:google).query_url(Geocoder::Query.new("..."))
 
 Replace `:google` with the lookup you are using and replace `...` with the address you are trying to geocode. Then visit the returned URL in your web browser. Often the API will return an error message that helps you resolve the problem. If, after reading the raw response, you believe there is a problem with Geocoder, please post an issue and include both the URL and raw response body.
 
+You can also fetch the response in the console:
+
+    Geocoder::Lookup.get(:google).send(:fetch_raw_data, Geocoder::Query.new("..."))
+
 
 Reporting Issues
 ----------------
-- 
GitLab