Right now, http.DefaultClient is used which can leave lingering goroutines until CloseIdleConnections is called. This is not desirable in multi-tenant applications or daemonized applications managed by the same go process. Preferably, a ClientContext like method that supplies an http.Client or http.Transport could be created for this purpose; a new option would also work as well, but may be a little bloaty.