Ignoring invalid headers for requests #145
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.
The idea for this PR came up from this discussion in the hyper repo.
This PR tries to make a request version of the
ParserConfig::ignore_invalid_headers_in_responses
configuration, introduced asParserConfig::ignore_invalid_headers_in_requests
, so that we can also ignore invalid headers in requests.In order to achieve that avoiding breaking backwards compatibility, it splits the
ParserConfig
struct used forparse_headers_iter_uninit
intoParserConfig
andHeaderParserConfig
.Happy to reassess the tests or the approach.