feat(client): Apply configuration sequentially #391
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request focuses on refactoring the
ClientBuilder
andConfig
structures in thesrc/client/http.rs
file to improve the handling of TLS configurations and headers. The most important changes include the introduction of aTlsConfig
structure, removal of theHttpContext
structure, and updates to various methods to reflect these changes.Refactoring and improvements:
HttpContext
withTlsConfig
inConfig
struct andClientBuilder
methods. [1] [2] [3]headers
andheaders_order
fields toConfig
struct and updated related methods to use these fields. [1] [2] [3]ClientBuilder
methods to use the newTlsConfig
structure for TLS-related configurations. [1] [2] [3]impersonate
method to update theConfig
struct directly with values from theHttpContextProvider
.