A middleware that inserts the value into the [`Extensions`](http::Extensions) during the call. This is a good way to inject extensions to middleware

A `ClientBuilder` is used to build a [`ClientWithMiddleware`]. [`ClientWithMiddleware`]: crate::ClientWithMiddleware

The default [`RetryableStrategy`] for [`RetryTransientMiddleware`](crate::RetryTransientMiddleware).

The default [`ReqwestOtelSpanBackend`] for [`TracingMiddleware`]. Note that it doesn't include the `url.full` field in spans, you can use [`SpanBacken

this is meant to be semi-private, same as reqwest's pending

Request-Line = Method SP Request-URI SP HTTP-Version CRLF

Injector used via opentelemetry propagator to tell the extractor how to insert the "traceparent" header value This will allow the propagator to inject

When attached to a [`ClientWithMiddleware`] (generally using [`with_init`]), it is run whenever the client starts building a request, in the order it

[`ReqwestOtelSpanBackend`] allows you to customise the span attached by [`TracingMiddleware`] to incoming requests. Check out [`reqwest_otel_span`] d

`RetryTransientMiddleware` offers retry logic for requests that fail in a transient manner and can be safely executed again. Currently, it allows set

A strategy to create a [`Retryable`] from a [`Result<reqwest::Response, reqwest_middleware::Error>`] A [`RetryableStrategy`] has a single `handler` f

This is a simple server that returns the responses given at creation time: [`self.raw_http_responses`] following a round-robin mechanism.

Similar to [`DefaultSpanBackend`] but also adds the `url.full` attribute to request spans. [`TracingMiddleware`]: crate::middleware::TracingMiddlewar

Middleware for tracing requests using the current Opentelemetry Context.