Fix bug where last few bytes on socket go unread (#795)

**Issue:** We're occasionally seeing errors when the server sends an HTTP response with a `Connection: close` header (meaning it intends to close the connection after the response is sent). The server is sending the full response, then immediately hanging up. But the last few bytes of the response never make it to the HTTP client. **Description of changes:** Update submodules, bringing in this fix: awslabs/aws-c-io#642 ``` aws-c-auth v0.7.17 -> v0.7.22 aws-c-cal v0.6.11 -> v0.6.15 aws-c-common v0.9.15 -> v0.9.21 aws-c-http v0.8.1 -> v0.8.2 aws-c-io v0.14.7 -> v0.14.9 aws-c-mqtt v0.10.3 -> v0.10.4 aws-c-sdkutils v0.1.15 -> v0.1.16 s2n v1.4.11 -> v1.4.16 ```
awslabs · Jun 13, 2024 · ae87528 · ae87528
1 parent 262e10f
commit ae87528
Show file tree

Hide file tree

Showing 8 changed files with 8 additions and 8 deletions.
diff --git a/crt/aws-c-auth b/crt/aws-c-auth
diff --git a/crt/aws-c-cal b/crt/aws-c-cal
diff --git a/crt/aws-c-common b/crt/aws-c-common
diff --git a/crt/aws-c-http b/crt/aws-c-http
diff --git a/crt/aws-c-io b/crt/aws-c-io
diff --git a/crt/aws-c-mqtt b/crt/aws-c-mqtt
diff --git a/crt/aws-c-sdkutils b/crt/aws-c-sdkutils
diff --git a/crt/s2n b/crt/s2n