You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You don't have to worry about the body returned (it will be garbage collected by Go). The connection to the website can stay alive for the keep-alive duration if the connection supports it.
It seems that
fasthttp
doesn't provide any resource cleaning method for its http client:So do I need to worry about resource leaking problem? How dose fasthttp manage http connections?
Thanks!
The text was updated successfully, but these errors were encountered: