From a81f6540dc48b40e71493d6398a4838226770d27 Mon Sep 17 00:00:00 2001 From: "jar@google.com" Date: Fri, 12 Dec 2008 17:33:10 +0000 Subject: Remove overly aggressive assert I was seeing this assertion when a filter translated broken data into a meta-refresh (in the experimental SDCH filter decode). r=mbelshe Review URL: http://codereview.chromium.org/13771 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6895 0039d316-1c4b-4281-b951-d872f2087c98 --- net/url_request/url_request_job.cc | 9 --------- 1 file changed, 9 deletions(-) diff --git a/net/url_request/url_request_job.cc b/net/url_request/url_request_job.cc index 6e969b2..98712a5 100644 --- a/net/url_request/url_request_job.cc +++ b/net/url_request/url_request_job.cc @@ -407,15 +407,6 @@ void URLRequestJob::NotifyDone(const URLRequestStatus &status) { // the response before getting here. DCHECK(has_handled_response_ || !status.is_success()); - // In the success case, we cannot send the NotifyDone now. It can only be - // sent after the request is completed, because otherwise we can get the - // NotifyDone() called while the delegate is still accessing the request. - // In the case of an error, we are fre - if (status.is_success()) { - // If there is data left in the filter, then something is probably wrong. - DCHECK(!FilterHasData()); - } - // As with NotifyReadComplete, we need to take care to notice if we were // destroyed during a delegate callback. if (request_) { -- cgit v1.1