A minor tweak of r5245.  I'm more confident that WinHTTP knows a transaction is complete when WinHttpReadData returns a zero byte count.  So it's safer to NOT notify the request throttle when WinHttpReadData returns a nonzero byte count, even if we have read the number of bytes specified in the Content-Length response header.  I verified that this is still enough to fix the bug (unresponsiveness).
A minor tweak of r5245.  I'm more confident that WinHTTP
knows a transaction is complete when WinHttpReadData returns
a zero byte count.  So it's safer to NOT notify the request
throttle when WinHttpReadData returns a nonzero byte count,
even if we have read the number of bytes specified in the
Content-Length response header.  I verified that this is
still enough to fix the bug (unresponsiveness).

R=darin
BUG=4302

Review URL: http://codereview.chromium.org/10867

git-svn-id: http://src.chromium.org/svn/trunk/src@5415 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

Former-commit-id: a6a86be1dc6d8d83b4df9743d4eb0944e808f007
meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser