Due to stream's client not storing the Headers, hackney_response:maybe_close ignores the "Connection: close" response header. This causes that a soon-to-be-closed socket is put back in the pool, potentionally being delivered to other client.
With these changes, hackney_response:maybe_close handles the way hackney_stream stores the connection value
Due to stream's client not storing the Headers, hackney_response:maybe_close ignores the "Connection: close" response header. This causes that a soon-to-be-closed socket is put back in the pool, potentionally being delivered to other client.
With these changes, hackney_response:maybe_close handles the way hackney_stream stores the connection value