Jeremiah Senkpiel
Jeremiah Senkpiel
I don't follow, why should someone have to install a middleware to set typed headers easily? This is not just about auth.
Just to be clear, my suggestion here is to hopefully avoid something like: `.header()` & `.header_typed()` or `.header_parts()` & `.header(Typed)`. Although I suppose the latter wouldn't be terrible, but also...
For posterity, tracking issue for typed headers progress: https://github.com/http-rs/http-types/issues/99
> - Persistent connections do not seem to be working with surf. I'm using async-h1 as a default-client, but I'm still seeing a SYN/FIN for every request. Is this supposed...
If you run `cargo update`, you should now get connection pooling while using the `h1_client` feature. You may also need to enable tls separately on `http-client` until the next Surf...
See https://github.com/http-rs/http-types/pull/175 - likely to picked back up soon over there, unsure how or when that will impact a full surf api for this.
I don't have any investment in this anymore. Someone else will need to pick it up.
semver-major because we re-export http-client stuff and it's also semver-major over there (And would also be semver-major if it were all here.)
~~The HttpClient thing is, frankly, largely separate and can be done already, separately from the concerns of the rest.~~ ~~This isn't really true, because we can't have it be `Clone`...
For the rest, I think that would necessitate a `ClientBuilder` ... Stated again, a base URL is not the only reason to use a Surf client: - Pooling already exists...