JongHyun Kim
JongHyun Kim
Thank you for sharing the earlier discussions and the follow up. It would be great if the client supports this behavior somehow even though Hyper doesn't have explicit support. I...
Also, to add few thoughts, I think it makes sense to add it to the Hyper explicitly since it is listed in RFC https://www.rfc-editor.org/rfc/rfc9110#name-expect.
Hi, I was able to implement 100 Continue behavior by using `set_on_informational_hook` that you exposed. Thanks! Let me create an example code as an Hyper example. I think it would...
Created a new PR to add a new example
I also had the same ask while using with Bedrock. To resolve the issue, I just created a new pull request to add the profile support. Please let me know...
Hi, My main goal is the first one, preserving the header case while forwarding the request and response.
Sounds good! I can definitely follow up with PR. Just to clarify, I was thinking to only expose `preserve_header_order` API as a part of Client Conn Builder to allow the...
Thank you for clarification. I'll raise a PR soon
I went through the codes in https://github.com/hyperium/hyper/blob/master/src/proto/h1/role.rs and found that there is no actual logic to use `OriginalHeaderOrder` in encoding the headers into the bytes. I believe it is because...
Sorry for late. I double checked and found the ask was to expose this feature for the server. https://github.com/hyperium/hyper/blob/1c70fab64e90f90025eab364beda927044e356fc/src/proto/h1/role.rs#L165 The change was about enhancing `h1_parser_config`, and found it is not...