tree ec6019e9d3eb68c19c7d279de1f6a99e27737959
parent 28385db6e1e480815f72f9629fa9dab48b453399
author David Benjamin <davidben@google.com> 1525589147 -0400
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1525719900 +0000

Fix bssl handling of buffered read data.

If the peer sends us one record that exceeds buffer, the socket will no
longer flag as readable, because data has been consumed, but SSL_read
should still be called to drain data. bssl would instead not notice and
only surface the data later on.

This can (currently) be reproduced by sending "HEAD / HTTP/1.1" to
www.google.com.

Change-Id: I73cdbe104ba6be56fc033429999e630f0eb852d8
Reviewed-on: https://boringssl-review.googlesource.com/28166
Commit-Queue: Steven Valdez <svaldez@google.com>
Reviewed-by: Steven Valdez <svaldez@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>