Repository navigation
-
#826 a request no longer fails with
client error (SendRequest)when the server closes an idle keep-alive connection just as the request goes out on it: Goose sent each request once and counted the server's idle close as a failure, where a browser sends the request again; Goose now sends a GET, HEAD, PUT, DELETE, OPTIONS or TRACE request once more, on a new connection, when its connection closes or is reset before the response head arrives, and records one request with the time of both attempts; it never sends a POST or PATCH again, as it can't see whether part of the response arrived, unlike a browser, and never sends a timeout or connect error again; a run that sent requests again ends with the info lineN requests were sent again after the server closed a reused connection before responding -
#824 the Goose Book follows the Tag1 brand: self-hosted Poppins type, the Tag1 colors, one light and one dark look in place of mdBook's six themes, a Goose favicon, a GitHub link in the menu bar, and print styles; the title page is restaged around the live dashboard, the Goose 0.19 benchmark against k6 and Locust, and recent posts from the Tag1 blog
-
#822 users start much faster and use less memory on Linux, where Goose now reads the system's root certificates once per process for the clients it builds, instead of once for every client that checks certificates; if a load test installs its own rustls crypto provider or adds a CA during a run, see the Book's TLS section
-
#822 behavior change: the clients Goose builds, including those from
GooseClientBuilder, now use HTTP/1.1 over rustls whenever they check certificates, even with reqwest'shttp2ornative-tlsfeature on (anyreqwest0.13 dependency with default features turns onhttp2); to keep HTTP/2 or native TLS, pass your ownreqwest::ClientBuildertoGooseUser::set_client_builder, as the Book's TLS section explains -
#814 examples read every response body to the end, so a user reuses its HTTP/1.1 connection:
examples/umamiandexamples/drupal_memcachedropped every static asset's response with its body unread, which could close its connection (against Varnish, the Umami example opened a new connection for two thirds of its requests and cut large assets off mid transfer), and the crate docs, other examples and the Book taught the same idiom withlet _goose = user.get(...); addsGooseResponse::discard_body, which reads a body to the end a chunk at a time, throws it away and returns the number of bytes read, used wherever a body was dropped, and a Book tip, "Read every response body"; request times are unchanged, while a transaction that now reads a body it used to drop takes longer by the download, and so does its scenario