fixup! Changed policy decision mechanism to use content resource throttle API

Remove incorrect DCHECK. There won't be any response headers for a
request in case it was loaded thorugh protocols like file://. An easy
way to trigger the DCHECK is to simply run:

./out.x64/Debug/ubrowser <path to some html file>
Reviewed by: Piotr Grad, SeungSeop Park

Change-Id: Icb7cd589d759ab47df06d706156f3763e93089d3
Signed-off-by: Piotr Tworek <p.tworek@samsung.com>

diff --git a/tizen_src/impl/API/ewk_policy_decision_private.cc b/tizen_src/impl/API/ewk_policy_decision_private.cc
index eed545c..8e6c88f 100644 (file)
--- a/tizen_src/impl/API/ewk_policy_decision_private.cc
+++ b/tizen_src/impl/API/ewk_policy_decision_private.cc
@@ -39,7 +39,6 @@ _Ewk_Policy_Decision::_Ewk_Policy_Decision(const GURL &request_url,
   DCHECK(request);
 
   net::HttpResponseHeaders* response_headers = request->response_headers();
-  DCHECK(response_headers);
 
   ParseUrl(request_url);
   if (response_headers) {