0936f1b875
Merge from Widevine repo of http://go/wvgerrit/53640 While HttpSocket supports both secure and insecure requests, the error-handling code in HttpSocket::Read() was written assuming that the insecure code path was previously taken. This resulted in spurious and misleading error messages being printed when an SSL error occurred, and it also meant that retryable SSL responses were not being retried. Also, the code for detecting a closed connection was technically incorrect, although a quirk of BoringSSL meant that it happened to work well enough to go unnoticed. This patch adds separate SSL error handling from the non-secure error handling. It correctly checks for a closed connection. It will retry retryable errors after a delay. And it prints the correct BoringSSL error when an unrecoverable error occurs. There should be no change in behavior for insecure connections. Bug: 77338045 Test: CE CDM Unit Tests Test: tested as part of http://go/ag/4674759 Change-Id: I8c45ca5771f22c11716d2e3649de91ab1acc1954