Skip to content

Allow insensitive header sending #2635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
j-mendez opened this issue Apr 11, 2025 · 3 comments
Closed

Allow insensitive header sending #2635

j-mendez opened this issue Apr 11, 2025 · 3 comments
Labels
B-upstream Blocked: upstream. Depends on a dependency to make a change first.

Comments

@j-mendez
Copy link

Some older web servers require headers to be title case. We need to determine if a header starts with title case for only certain headers.
If it is insensitive the headers should not be lowercased by default?

@seanmonstar
Copy link
Owner

There is an option http1_title_case_headers. Is that enough for your needs?

@j-mendez
Copy link
Author

Hi, @seanmonstar no we need to be able to have some headers lowercase and some caps. The google chrome browser sends headers this way and we need to mimic the real world handling of it since some websites have strict anti-bot defenses that require this.

@seanmonstar seanmonstar added the B-upstream Blocked: upstream. Depends on a dependency to make a change first. label Apr 11, 2025
@seanmonstar
Copy link
Owner

Ah, well in that case, this is blocked by support in hyper: hyperium/hyper#2695

That issue needs work to design a public API for the experimental feature, and then reqwest could support it.

@seanmonstar seanmonstar closed this as not planned Won't fix, can't repro, duplicate, stale Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-upstream Blocked: upstream. Depends on a dependency to make a change first.
Projects
None yet
Development

No branches or pull requests

2 participants