http2: Fix busy loop when EOF is encountered
Previously we did not handle EOF from underlying transport socket and wrongly just returned error code CURL_AGAIN from http2_recv, which caused busy loop since socket has been closed. This patch adds the code to handle EOF situation and tells the upper layer that we got EOF.
parent
1d2ffb47
Please register or sign in to comment