-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spec doesn't finalize connection on network error #948
Comments
Or maybe the spec assumes that GC should handle this? #950 |
Indeed. I believe the connection should be terminated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been reading through the spec a few times now and there seems to be missing a connection cleanup somewhere.
The problem is that whenever we replace
response
with anetwork error
(example) that means that we no longer will read that response nor do we close the associated connection. Effectively leaking the connection.Is this a bug in the spec or am I missing something? Maybe we need a "terminate" in
fetch finale
?The text was updated successfully, but these errors were encountered: