You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
http1 options are exposed through client::Builder but not lower-level client::conn::Builder interface #2461
http1_read_buf_exact_size, http1_max_buf_size, and http1_title_case_headers are all configuration methods on hyper::client::Builder, but not hyper::client::conn::Builder. I notice that the methods are present on the latter type but are pub(super) rather than pub.
Currently, I believe users of the conn interface are stuck with the default values of these settings. Are there any reasons not to make these pub with similar docstrings to the higher-level API? I'd be happy to provide a PR if not.
I believe it is simply an oversight. I'd say more of the builder options also make sense on the conn types (besides pooling, listener config, the obvious).
Activity
seanmonstar commentedon Mar 11, 2021
I believe it is simply an oversight. I'd say more of the builder options also make sense on the
conntypes (besides pooling, listener config, the obvious).Expose http09 and http1 options on low-level
feat(client): expose http09 and http1 options on `client::conn::Build…