Might `Agent` be caching network info in a way that survives the destructor? about ureq HOT 5 CLOSED

Hi! Welcome to ureq!

What SSL backend are you using here? Which features are turned on for ureq in Cargo.toml?

from ureq.

Thank you! And thanks for all the hard work that's gone into this library -- it's great to have such a standard for HTTP requests.

I believe we use OpenSSL:

$ dpkg -l | grep -i openssl
ii  openssl                   1.1.1n-0+deb11u3             amd64        Secure Sockets Layer toolkit - cryptographic utility

As for ureq feature spec:

ureq = { version = "2.6.2", features = ["cookies", "json"] }

Also, Rust version:

$ rustc --version
rustc 1.65.0 (897e37553 2022-11-02)

from ureq.

FYI tracked this down to what I believe was memory-related connection mismanagement in this Go service we have to make some requests to (closing)

from ureq.

Great, glad you solved it! BTW, given the features you showed from Cargo.toml you're using the rustls TLS backend, which is the default for ureq.

And you're correct that the agent you're defining is dropped at the end of each function call, and that in turn drops all the connections it held.

from ureq.

@jsha thanks and yes, all makes sense (sorry about SSL / TLS miscommunication - opened this ticket quickly and "under the gun")

from ureq.