Skip to content

Bad eof detection#10

Merged
kpacha merged 6 commits intomasterfrom
sc-821/bad_eof_detection
Sep 3, 2025
Merged

Bad eof detection#10
kpacha merged 6 commits intomasterfrom
sc-821/bad_eof_detection

Conversation

@dhontecillas
Copy link
Copy Markdown
Contributor

When partials reads had been made (because of slow response, or chunked response), the response was being cached as if it was already completed.

The underlying network connection reader does not support returning an EOF, so, unless we know the size of response (when the server provides a Content-Length) we are not able to detect the end of the body (is the calling function that is for example parsing a streaming json, that knows when it has finished reading it .. so when it closes the body, we know that the "body content" was readed).

@dhontecillas
Copy link
Copy Markdown
Contributor Author

I know there is PR updating the github action to execute the tests, but it was failing the build here, and I've just update it here too.

kpacha
kpacha previously approved these changes Sep 3, 2025
@kpacha kpacha merged commit 221b01a into master Sep 3, 2025
6 checks passed
@kpacha kpacha deleted the sc-821/bad_eof_detection branch September 3, 2025 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants